LiveActive security incident?Get immediate response
CVE Record

CVE-2024-25904: WordPress TinyMCE Professional Formats and Styles Plugin <= 1.1.2 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-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.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-25904 is a CSRF issue in the WordPress TinyMCE and TinyMCE Advanced Professsional Formats and Styles plugin through version 1.1.2. It may let an attacker trick a user into causing an unintended change. Reported impact is limited integrity only, with no stated data theft or outage impact.

Executive priority

Treat as a routine WordPress plugin hygiene issue, not an emergency, unless the plugin is widely deployed on business-critical sites. Prioritize inventory and vendor guidance because no fixed version is provided in the source bundle.

Technical view

The CVE describes CWE-352 cross-site request forgery in David Stockl’s WordPress plugin through 1.1.2. CVSS 3.1 is 4.3: network reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, no confidentiality or availability impact, and low integrity impact.

Likely exposure

Exposure is limited to WordPress installations using the named plugin at version 1.1.2 or earlier. The source bundle does not identify the vulnerable endpoint, affected action, fixed version, or whether the plugin remains maintained.

Exploitation context

The bundle does not show CISA KEV listing or any cited evidence of active exploitation. Exploitation requires user interaction per CVSS. The exact action an attacker could cause is not described in the provided sources, so operational impact should be validated against vendor guidance.

Researcher notes

Evidence is thin: the record identifies CSRF, affected versions through 1.1.2, and CVSS impact only. Do not assume the vulnerable endpoint, required victim role, nonce failure pattern, or remediation without confirming from vendor or Patchstack details.

Mitigation direction

  • Inventory WordPress sites for the affected plugin and versions through 1.1.2.
  • Check vendor or Patchstack guidance for a fixed release or official mitigation.
  • Disable or remove the plugin where it is not business-critical.
  • Monitor administrative changes for unexpected formatting or editor configuration updates.

Validation and detection

  • Confirm plugin slug and version from WordPress administration or asset inventory.
  • Review Patchstack and CVE records for any updated fix or mitigation details.
  • Check whether affected sites expose administrative users to untrusted links or content.
  • Verify no unexpected editor-format configuration changes occurred around suspicious user activity.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-25904 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2024-25904Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
David StocklTinyMCE and TinyMCE Advanced Professsional Formats and Stylestinymce-and-tinymce-advanced-professsional-formats-and-styles, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.