Security readout for executives and security teams
Plain-English summary
CVE-2025-46245 affects the WordPress CM Ad Changer plugin through version 2.0.5. It is a CSRF issue, meaning an attacker may be able to trick a logged-in site user into making an unintended plugin-related change. The rated impact is limited, but affected WordPress sites should verify plugin exposure and vendor guidance.
Executive priority
Treat as a normal-priority WordPress plugin remediation item. It is not currently supported by evidence of active exploitation, but exposed sites using the affected plugin should be reviewed and updated or mitigated when vendor guidance is available.
Technical view
The issue is CWE-352 Cross-Site Request Forgery in CreativeMindsSolutions CM Ad Changer, package cm-ad-changer, affecting versions through 2.0.5. CVSS 3.1 is 4.3: network exploitable, low complexity, no attacker privileges, user interaction required, unchanged scope, low integrity impact, no confidentiality or availability impact.
Likely exposure
Exposure is limited to WordPress sites with CM Ad Changer installed at version 2.0.5 or earlier. The source bundle does not identify affected endpoints, required victim role, fixed version, or default exploitability beyond the CVSS attributes.
Exploitation context
No active exploitation is indicated in the provided sources, and the CVE is not listed as KEV. Successful abuse requires user interaction and would primarily affect integrity, not data confidentiality or service availability, according to the CVSS vector.
Researcher notes
Public detail is sparse. The record confirms CSRF, affected plugin and version range, CVSS, and Patchstack reference, but does not provide endpoint-level details, proof-of-concept status, or a named patched release in the supplied bundle.
Mitigation direction
- Inventory WordPress sites for the CM Ad Changer plugin.
- If installed, identify whether the version is 2.0.5 or earlier.
- Check CreativeMindsSolutions and Patchstack guidance for updates or workarounds.
- Restrict administrative access and avoid clicking untrusted links while logged in.
- Remove or disable the plugin if business use is not required.
Validation and detection
- Confirm plugin presence and version in WordPress administration or asset inventory.
- Compare installed versions against the affected range through 2.0.5.
- Review vendor and Patchstack pages for any newly published fixed version.
- Check whether compensating controls limit admin-session exposure.
- Document affected sites, owners, and remediation status.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCVE-2025-46245 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- 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
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4PatchstackVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/Wordpress/Plugin/cm-ad-changer/vulnerability/wordpress-cm-ad-changer-2-0-5-cross-site-request-forgery-csrf-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.