Cross-Site Scripting (XSS) in ShareOpenly (WordPress plugin) (CVE-2026-48094)
Summary
Cross-site scripting in ShareOpenly (WordPress plugin) (CVE-2026-48094). Risk of unauthorized operations or information disclosure. Exploitable via href.
Original description
The description as published by the source.
The ShareOpenly WordPress plugin prior to version 1.2.1 contains a Cross-Site Scripting vulnerability caused by the absence of WordPress's esc_url() escaping function on the $url variable before it is rendered into HTML content. This variable is constructed from home_url( add_query_arg( array(), $wp->request ) ) and is concatenated directly into an HTML href attribute on every singular post or page where the plugin's sharing link is displayed. WordPress's security handbook mandates that every URL placed in HTML output must be passed through esc_url(), which both HTML-encodes special characters (converting ", <, > into their safe HTML entity equivalents) and strips dangerous URI schemes such as javascript: and data:. The omission of this function means that if the $url value ever contains HTML-special characters or a dangerous URI scheme — through a home_url WordPress filter applied by another plugin or theme, through certain web server or hosting configurations, or through future code changes — the unescaped content will be injected verbatim into the rendered HTML of every post or page on the site. Version 1.2.1 contains a patch for the issue.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-48094 has been found in ShareOpenly (WordPress plugin).
Attackers can target a specific entry point like href over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "ShareOpenly (WordPress plugin) CVE-2026-48094" on the vendor's site.
CVE-2026-48094 (ShareOpenly (WordPress plugin)) — CWE-79
Attack surface: href / home_url
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Cross-site scripting (XSS) (CWE-79) exists in ShareOpenly (WordPress plugin). Attackers reach the vulnerable code path via href.
Check the vendor advisory for the affected versions of ShareOpenly (WordPress plugin). Attack surface: href / home_url.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで ShareOpenly (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。