CVE-2026-48094: ShareOpenly has Cross-Site Scripting (XSS) via Missing esc_url() on Shared URL in Content Output

Published Aug 7, 2026
·
Updated

The ShareOpenly WordPress plugin prior to version 1.2.1 contains a Cross-Site Scripting vulnerability caused by the absence of WordPress's escurl() escaping function on the $url variable before it is rendered into HTML content. This variable is constructed from homeurl( addqueryarg( 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 escurl(), 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 homeurl 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.

Affected Software

1 affected component
ShareOpenly WordPress plugin<1.2.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade wordpress/shareopEnly to a version that resolves this vulnerability.

    Fixed in 1.2.1
  2. Configuration

    In the plugin code path that renders the sharing link into an HTML href attribute on singular post/page views, escape the constructed URL using WordPress's esc_url() (WordPress security handbook requirement) before output.

    ShareOpenly WordPress plugin Use WordPress esc_url() for shared URL output = esc_url($url)

Event History

Aug 7, 2026
CVE Published
via MITRE·12:37 PM
Data Sourced
via MITRE·12:37 PM
DescriptionWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-48094?

CVE-2026-48094 has a risk score of 31, indicating a moderate level of severity.

2

How do I fix CVE-2026-48094?

To resolve CVE-2026-48094, update the ShareOpenly WordPress plugin to version 1.2.1 or later.

3

What causes the vulnerability in CVE-2026-48094?

CVE-2026-48094 is caused by the lack of the `esc_url()` function which leads to Cross-Site Scripting (XSS) vulnerabilities.

4

Which library is affected by CVE-2026-48094?

The vulnerability affects the ShareOpenly WordPress plugin prior to version 1.2.1.

5

What type of vulnerability is CVE-2026-48094?

CVE-2026-48094 is classified as a Cross-Site Scripting (XSS) vulnerability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203