CVE-2025-46495: WordPress Drop Caps plugin <= 2.1 - CSRF to XSS vulnerability
Cross-Site Request Forgery (CSRF) vulnerability in tomontoast Drop Caps drop-caps allows Stored XSS.This issue affects Drop Caps: from n/a through <= 2.1.
Security readout for executives and security teams
Plain-English summary
CVE-2025-46495 affects the WordPress Drop Caps plugin through version 2.1. A logged-in user could be tricked into making a request that stores malicious script in the site. Business impact is usually limited, but it can affect visitors or administrators who view the poisoned content.
Executive priority
Treat this as a moderate WordPress plugin risk. Prioritize internet-facing sites and sites with multiple content administrators, but it is not supported as emergency-level without evidence of active exploitation or a critical impact path.
Technical view
The source describes a CSRF weakness in tomontoast Drop Caps drop-caps leading to stored XSS. CVSS 3.1 is 6.5 with network attack vector, low complexity, low privileges required, user interaction required, changed scope, and low confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to WordPress installations with the Drop Caps plugin installed and enabled at version 2.1 or earlier. The bundle does not identify affected configurations beyond the plugin and version range.
Exploitation context
The CVE is not listed as KEV in the supplied bundle, and no cited source states active exploitation. Exploitation requires user interaction and appears to require some authenticated privilege, based on the CVSS vector.
Researcher notes
Evidence is limited to the CVE metadata and Patchstack reference. The affected range is stated as through 2.1. Do not assume a patch version, exploitation in the wild, or additional affected products without vendor or advisory confirmation.
Mitigation direction
Inventory WordPress sites for Drop Caps/drop-caps version 2.1 or earlier.
Check vendor and Patchstack guidance for a fixed release or official mitigation.
Update the plugin if a vendor-supported fixed version is available.
Disable or remove the plugin where it is not business-critical.
Limit WordPress admin access to trusted users while exposure is assessed.
Validation and detection
Confirm whether Drop Caps is installed, enabled, and at version 2.1 or earlier.
Review WordPress admin change history for unexpected Drop Caps-related changes.
Inspect affected pages for unexpected stored script content.
Verify vendor or Patchstack advisory status before declaring remediation complete.
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.
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.
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.
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.