Tinymce And Tinymce Advanced Professsional Formats And StylesWordPress extension · Blackbam
CVE-2024-25904
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in David Stockl TinyMCE and TinyMCE Advanced Professsional Formats and Styles.This issue affects TinyMCE and TinyMCE Advanced Professsional Formats and Styles: from n/a through 1.1.2.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in TinyMCE and TinyMCE Advanced Professional Formats and Styles plugin versions through 1.1.2. The plugin lacks proper CSRF protection, allowing attackers to trick authenticated users into performing unintended actions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Tinymce And Tinymce Advanced Professsional Formats And StylesWordPress extension
<= 1.1.2CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Locate the plugin installationCheck your CMS plugins directory for a folder named containing 'tinymce-advanced-professional' or 'blackbam'. Common paths include /wp-content/plugins/ for WordPress or /plugins/ for other CMS platforms.Affected if The plugin folder exists in your system
-
Identify the installed versionOpen the main plugin file (typically named index.php, main.php, or the plugin's primary PHP file) and look for a version comment or constant in the file header. Alternatively, check for a version.xml, composer.json, or plugin.json file if one exists.Affected if The reported version is 1.1.2 or lower, or no version is discoverable (indicating it may be an older release)
-
Inspect state-changing functions for CSRF protectionSearch the plugin's PHP files for form submissions and AJAX handlers that modify data (insert, update, delete operations). Look for calls to check_admin_referer, wp_verify_nonce, or similar nonce verification functions within these handlers.Affected if State-changing functions lack nonce verification or token validation checks
-
Check for Origin/Referer header validationSearch the plugin's PHP code for $_SERVER['HTTP_ORIGIN'], $_SERVER['HTTP_REFERER'], or similar server variable checks that validate request origin before processing state-changing operations.Affected if No origin or referer header validation is performed before executing sensitive actions
-
Review plugin configurationCheck if the plugin provides an admin settings page and inspect whether the settings form includes a hidden nonce token field (look for input type='hidden' name with '_nonce' or similar pattern).Affected if Admin forms lack anti-CSRF token fields
You are affected if the Blackbam Tinymce/TinyMCE Advanced Professional Formats and Styles plugin is installed at version 1.1.2 or lower and the plugin code does not implement nonce tokens or Origin/Referer validation for state-changing operations.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement anti-CSRF tokens (synchronizer token pattern) for state-changing operations and validate Origin/Referer headers to ensure requests originate from legitimate sources.
Fix this in Tinymce And Tinymce Advanced Professsional Formats And Styles
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-25904 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-25904 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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