dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-26582

HIGH · 7.1 CVSS v3.1 Published 2025-02-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Blackbam TinyMCE Advanced qTranslate fix editor problems tinymce-advanced-qtranslate-fix-editor-problems allows Stored XSS.This issue affects TinyMCE Advanced qTranslate fix editor problems: from n/a through <= 1.0.0.

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

A Cross-Site Request Forgery (CSRF) vulnerability in the Blackbam TinyMCE Advanced qTranslate fix editor plugin allows attackers to inject malicious scripts through the TinyMCE editor that get stored (Stored XSS). The lack of anti-CSRF token validation on editor submission forms enables forced actions by authenticated users, leading to persistent malicious script execution.

MitigationImplement anti-CSRF tokens (nonces) on all editor forms and actions, and apply proper output encoding/sanitization to all user-supplied content in the TinyMCE editor to prevent XSS.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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. Identify if the Blackbam TinyMCE Advanced qTranslate fix plugin is installed
    Access your WordPress admin panel, navigate to Plugins, and look for 'Blackbam TinyMCE Advanced qTranslate fix' in the installed plugins list. Alternatively, check your wp-content/plugins directory for a folder named similarly to 'tiny-mce-advanced-qtranslate' or containing 'blackbam'.
    Affected if The plugin is present in the installation
  2. Determine the installed plugin version
    In the WordPress plugin admin page, click on the plugin name to view its details, or check the main plugin PHP file for a 'Version' header comment. If using a file manager or CLI, look in the plugin root directory for a readme.txt or the primary plugin PHP file.
    Affected if The version is unknown, unpatched, or cannot be verified against fixed versions
  3. Verify the TinyMCE editor is accessible to users
    Check if the TinyMCE editor component is enabled and accessible. In WordPress, navigate to Settings > TinyMCE Advanced (or similar editor settings) and confirm the editor loads for content creation. For qTranslate-X or multilingual setups, verify the editor appears when creating or editing posts/pages.
    Affected if The TinyMCE editor is active and available to authenticated users
  4. Inspect editor submission forms for anti-CSRF protection
    Use browser developer tools (F12) to view the HTML source of any form that submits content through the TinyMCE editor (e.g., post edit forms, page creation forms). Look for a hidden input field containing a nonce value (commonly named '_wpnonce', 'nonce', or 'security') or check if the form includes a token in its action URL or as a custom header.
    Affected if The editor submission forms lack a CSRF token (nonce) field or the token is not validated server-side
  5. Check for stored malicious scripts in editor content
    Query your database for any post content containing suspicious patterns. In phpMyAdmin or via CLI, run: SELECT * FROM wp_posts WHERE post_content LIKE '%<script%' OR post_content LIKE '%onload=%' OR post_content LIKE '%onerror=%'. Review any results to see if they originated from the TinyMCE editor submission.
    Affected if Stored XSS payloads are present in post/page content that was submitted through the affected editor interface

A user is affected if the Blackbam TinyMCE Advanced qTranslate fix plugin is installed, the TinyMCE editor is accessible, and editor submission forms lack proper anti-CSRF token validation, potentially allowing stored XSS attacks.

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

Implement anti-CSRF tokens (nonces) on all editor forms and actions, and apply proper output encoding/sanitization to all user-supplied content in the TinyMCE editor to prevent XSS.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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