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

CVE-2026-6565

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-27
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 Style Kits – Advanced Theme Styles for Elementor, Elementor Kits & Elementor Patterns plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the '/wp-json/agwp/v1/tokens/save' endpoint kit title parameter in versions up to, and including, 2.5.0 due to insufficient input sanitization and output escaping in an admin attribute context. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 · moderate confidence

The Style Kits WordPress plugin fails to properly sanitize and escape the kit title parameter in the /wp-json/agwp/v1/tokens/save REST API endpoint, allowing authenticated users with contributor-level access or higher to inject persistent malicious scripts that execute when other users view affected pages.

MitigationUpdate the plugin to a version that addresses this vulnerability (check vendor advisories for patched version), and ensure all user-supplied input in the kit title parameter is sanitized using functions like sanitize_text_field() before storage and properly escaped on output.

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 Style Kits plugin is installed
    Navigate to WordPress admin > Plugins and search for 'Style Kits', or run command: wp plugin list --search='style-kits'
    Affected if Plugin is not installed or not found in the plugins list
  2. Check installed version of Style Kits
    In WordPress admin > Plugins, click on Style Kits to view version details, or run: wp plugin list --search='style-kits' --field=version
    Affected if Version is 2.5.0 or lower (the vulnerability exists in versions up to 2.5.0)
  3. Confirm REST API endpoint exists
    Make a GET request to /wp-json/ and look for the agwp/v1 route in the API index, or directly attempt to access /wp-json/agwp/v1/tokens/save
    Affected if The agwp/v1 REST API route is registered and accessible (this is the default state)
  4. Check for contributor-level user accounts
    In WordPress admin > Users, look for users with Contributor role, or run: wp user list --role=contributor
    Affected if At least one user with contributor-level permissions exists in the system

Your environment is affected if Style Kits plugin version is 2.5.0 or lower AND the REST API endpoint is accessible AND any contributor-level user account exists, enabling the stored XSS attack vector.

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 plugin to a version that addresses this vulnerability (check vendor advisories for patched version), and ensure all user-supplied input in the kit title parameter is sanitized using functions like sanitize_text_field() before storage and properly escaped on output.

Recommended fix Moderate confidence

Plugin version > 2.5.0 (latest available version from wordpress.org)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Style Kits – Advanced Theme Styles for Elementor' plugin
  4. Check if an update is available and update to the latest version (greater than 2.5.0)
  5. Alternatively, download the latest version from wordpress.org/plugins/analogwp-templates/ and upload via Plugins > Add New > Upload Plugin
  6. After updating, verify the kit title parameter at the '/wp-json/agwp/v1/tokens/save' endpoint is now properly sanitized

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6565 — 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-6565 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