Security readout for executives and security teams
Plain-English summary
CVE-2024-25932 is a CSRF issue in the WordPress Change Table Prefix plugin through version 2.0. An attacker would need to induce a user interaction, and the reported impact is limited integrity change, not data theft or outage.
Executive priority
Treat as a moderate hygiene issue for WordPress estates. It is not documented as actively exploited in the supplied evidence, but affected sites should be inventoried and remediated because successful abuse could alter site configuration integrity.
Technical view
The source bundle identifies CWE-352 in Manish Kumar Agarwal's change-table-prefix WordPress plugin through <=2.0. CVSS 3.1 is 4.3 with network attack vector, low complexity, no attacker privileges, required user interaction, unchanged scope, and low integrity impact only.
Likely exposure
Exposure is limited to WordPress sites with the Change Table Prefix plugin installed at version 2.0 or earlier. The bundle provides no CPEs and does not identify other affected products.
Exploitation context
The CVE is not listed as KEV, and the provided sources do not claim active exploitation. CSRF generally depends on a victim interaction, consistent with the CVSS UI:R signal, but the bundle does not provide endpoint-level details.
Researcher notes
Evidence is sparse. The bundle confirms CSRF, affected plugin through <=2.0, CVSS 4.3, and Patchstack references, but it does not provide a patched version, vulnerable action, proof of exploitation, or detailed remediation.
Mitigation direction
- Inventory WordPress sites for the change-table-prefix plugin and installed version.
- Check vendor, WordPress.org, or Patchstack guidance for a fixed version or advisory.
- Disable or remove the plugin where it is not operationally required.
- Limit WordPress administrator sessions to trusted environments where feasible.
- Monitor for unexpected table prefix or plugin configuration changes.
Validation and detection
- Confirm whether Change Table Prefix is installed on each WordPress instance.
- Record plugin versions and prioritize any installation at 2.0 or earlier.
- Review Patchstack and CVE records for updated remediation details.
- Check WordPress administrative audit logs for unexpected plugin setting changes.
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-2024-25932 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/change-table-prefix/vulnerability/wordpress-change-table-prefix-plugin-2-0-cross-site-request-forgery-csrf-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
- https://patchstack.com/database/vulnerability/change-table-prefix/wordpress-change-table-prefix-plugin-2-0-cross-site-request-forgery-csrf-vulnerability?_s_id=cveCVE reference, CVE · vdb-entry, x_transferred
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.