dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-7475

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Sky Addons plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the `sky-custom-scripts` custom post type in all versions up to, and including, 3.3.2. This is due to the custom post type being registered with `capability_type => 'post'` and `show_in_rest => true`, combined with insufficient input sanitization on the `sky_script_content` meta field and lack of output escaping when rendering scripts on the frontend. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts via the REST API that execute on every frontend page for all site visitors.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Sky Addons WordPress plugin has a stored XSS vulnerability in its 'sky-custom-scripts' custom post type. The post type is exposed via REST API with overly broad capabilities, and the 'sky_script_content' meta field lacks input sanitization while the frontend rendering lacks output escaping. An authenticated Author+ user can inject malicious scripts that execute on every frontend page view.

MitigationUpdate the Sky Addons plugin to version 3.3.3 or later which addresses the sanitization and escaping issues; alternatively, disable the plugin until an update is available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Sky Addons plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate Sky Addons. Note the version number displayed. Alternatively, check the plugin header in wp-content/plugins/sky-addons/plugin.php or use a database query on wp_options for option_name='active_plugins' and examine plugin files.
    Affected if The plugin is installed and the version is lower than 3.3.3, or the version cannot be determined.
  2. Confirm 'sky-custom-scripts' custom post type exists
    Query the WordPress database: SELECT * FROM wp_posts WHERE post_type='sky-custom-scripts' AND post_status='publish'; Or inspect WP_Query capabilities via theme or plugin that lists registered post types.
    Affected if The 'sky-custom-scripts' CPT exists and is publicly queryable.
  3. Check REST API exposure of vulnerable endpoint
    Send a GET request to /wp-json/wp/v2/sky-custom-scripts?per_page=100 or /wp-json/sky-addons/v1/scripts (endpoint varies by plugin version). Examine the response for exposed post objects containing meta fields.
    Affected if The REST API returns published 'sky-custom-scripts' posts with meta data accessible without additional authorization beyond standard authentication.
  4. Inspect sky_script_content meta field for malicious scripts
    Query the postmeta table: SELECT post_id, meta_key, meta_value FROM wp_postmeta WHERE meta_key='sky_script_content'; Examine each value for unescaped HTML tags, script tags, event handlers (onclick, onerror, etc.), or encoded payloads that may contain malicious JavaScript.
    Affected if Any sky_script_content meta value contains unsanitized HTML, script tags, or known malicious payload patterns.
  5. Verify frontend output lacks escaping
    View the source of any frontend page on the site. Search for content from the sky-custom-scripts posts appearing unescaped in the HTML, particularly within <script> tags, event handlers, or raw HTML injection points.
    Affected if Frontend pages render script content from sky-custom-scripts posts without proper HTML entity encoding or escaping.

A user is affected if Sky Addons plugin is installed with version lower than 3.3.3 (or unknown), the sky-custom-scripts CPT exists, and either the REST API exposes it or malicious script content exists in the sky_script_content meta field that renders unescaped on frontend pages.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Sky Addons plugin to version 3.3.3 or later which addresses the sanitization and escaping issues; alternatively, disable the plugin until an update is available.

Recommended fix Moderate confidence

Sky Addons version 3.3.3 or latest available release

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the Sky Addons plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from wordpress.org/plugins/sky-addons and upload it manually via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the version number reflects the fix (version 3.3.3 or higher)
  7. 7. Test that the sky-custom-scripts functionality works correctly post-update

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7475 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7475 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data