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

CVE-2026-2602

MEDIUM · 6.4 CVSS v3.1 Published 2026-03-29
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 Twentig plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'featuredImageSizeWidth' parameter in versions up to, and including, 1.9.7 due to insufficient input sanitization and output escaping. 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 · high confidence

The Twentig WordPress plugin fails to properly sanitize the 'featuredImageSizeWidth' parameter before storing it and escape it when outputting, allowing authenticated users with Contributor-level permissions or higher to inject malicious JavaScript that executes when other users view affected pages.

MitigationUpdate Twentig to version 1.9.8 or later which includes proper input sanitization for the featuredImageSizeWidth parameter and ensures all output is escaped.

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 Twentig plugin is installed
    Navigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and look for 'Twentig' in the list. Note the version number displayed.
    Affected if Twentig plugin is present in the plugins list
  2. Compare installed version against fixed version
    Compare the installed Twentig version to 1.9.8. Versions below 1.9.8 are affected. The version is shown in the Plugins page or can be checked in the plugin's main PHP file header.
    Affected if Installed version is lower than 1.9.8
  3. Confirm authenticated user access exists
    Check WordPress user roles: go to Users > All Users and verify if any accounts have Contributor, Author, Editor, or Administrator roles. These roles can access the vulnerable parameter.
    Affected if At least one user with Contributor-level or higher permissions exists on the site
  4. Inspect featuredImageSizeWidth setting in database
    Query the WordPress database (wp_postmeta or wp_options table depending on where Twentig stores settings) for the featuredImageSizeWidth parameter. Look for values containing script tags, javascript:, or HTML event handlers.
    Affected if The featuredImageSizeWidth parameter contains unescaped HTML or JavaScript code

You are affected if Twentig is installed with a version below 1.9.8 and you have users with Contributor-level permissions or higher who can access the plugin settings containing the featuredImageSizeWidth parameter.

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 Twentig to version 1.9.8 or later which includes proper input sanitization for the featuredImageSizeWidth parameter and ensures all output is escaped.

Recommended fix Moderate confidence

Twentig plugin version 1.9.8 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Twentig plugin
  4. If an update is available, click 'Update Now' to update to the latest version
  5. Alternatively, navigate to Dashboard > Updates and update the Twentig plugin from there
  6. After updating, verify the plugin is running version 1.9.8 or higher

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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