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

CVE-2026-10092

HIGH · 7.2 CVSS v3.1 Published 2026-06-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges 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 Cincopa video and media plug-in plugin for WordPress is vulnerable to Stored Cross-Site Scripting via cincopa Shortcode in Post Comments in all versions up to, and including, 1.163 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation is possible because the plugin processes the [cincopa] shortcode via a comment_text filter hook, allowing unauthenticated visitors who can post comments to supply a malicious shortcode argument that persists in the database.

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 Cincopa WordPress plugin fails to sanitize and escape shortcode attributes processed through the comment_text filter, allowing unauthenticated attackers to inject malicious JavaScript via [cincopa] shortcode arguments in comments. This stored payload persists in the database and executes whenever users view the affected comment.

MitigationUpdate the plugin to version 1.164 or later which includes proper input sanitization and output escaping; alternatively, disable the comment feature or deploy a WAF rule blocking shortcode injection in comments until the patch is applied.

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
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 Cincopa plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate Cincopa. Check the version number displayed. Alternatively, inspect the plugin header in wp-content/plugins/cincopa-video-gallery/wordpress-cincopa.php or similar main plugin file.
    Affected if Plugin version is installed but is lower than 1.164, or version cannot be determined (plugin may be outdated/unmaintained)
  2. Confirm comment functionality is accessible
    Navigate to Settings > Discussion in WordPress admin. Verify that "Allow people to post comments on new articles" is enabled. Also verify the site is not blocking comments via .htaccess or security plugins.
    Affected if Comments are enabled and publicly accessible - unauthenticated users can post comments containing shortcodes
  3. Search database for cincopa shortcodes in comments
    Run SQL query: SELECT comment_ID, comment_author, comment_content FROM wp_comments WHERE comment_content LIKE '%[cincopa%' ORDER BY comment_date DESC. Inspect the comment_content field for any attributes that appear unescaped or contain suspicious patterns like javascript:, onload=, onerror=, or eval().
    Affected if Any comments found containing [cincopa] shortcode with unescaped attribute values or malicious-looking payload patterns
  4. Test shortcode rendering in comment output
    View a published comment containing [cincopa] shortcode in a browser. Use browser developer tools (Inspect Element) to examine the rendered HTML around the shortcode output. Look for unescaped quote characters or HTML injection in attribute values.
    Affected if Shortcode attributes render as raw unescaped text in HTML (e.g., quotes appear as " or raw quotes instead of being escaped)
  5. Check comment moderation for existing malicious submissions
    Review pending and approved comments in WordPress admin under Comments. Look for any submissions containing shortcode syntax with unusual attribute patterns, especially those containing script tags, event handlers, or encoded payloads.
    Affected if Malicious comments with injected JavaScript exist in the database, whether pending approval or already published

A site is affected if the Cincopa plugin version is below 1.164, comments are enabled, and shortcode injection is possible in comment content that renders unescaped in the output.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 1.164 or later which includes proper input sanitization and output escaping; alternatively, disable the comment feature or deploy a WAF rule blocking shortcode injection in comments until the patch is applied.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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