Security readout for executives and security teams
Plain-English summary
A vulnerable WordPress plugin named “uninstall” could let an attacker trick an authorized user into triggering deletion of all database tables. That is a business-impacting failure mode because it can destroy site data. The public record does not provide severity scoring, exploit evidence, or detailed remediation notes.
Executive priority
Treat as urgent where the plugin is present, because the stated impact is deletion of all database tables. Prioritize inventory, version verification, and recovery readiness over broad emergency action.
Technical view
The CVE describes a CSRF flaw in the WordPress uninstall plugin before 1.2. The affected endpoint is wp-admin/admin-ajax.php?action=uninstall and the stated impact is deletion of all tables. The source bundle does not provide CVSS, CWE, CPE data, required user role, or patch notes beyond the version boundary.
Likely exposure
Exposure is likely limited to WordPress sites that installed the uninstall plugin in a version before 1.2. The source bundle lists no CPEs or vendor-specific affected inventory data.
Exploitation context
The CVE source describes a CSRF condition, but the bundle provides no evidence of active exploitation and KEV is false. The wp-admin path implies administrative context, but required privileges are not stated.
Researcher notes
Evidence is sparse. The public record names the vulnerable plugin, version boundary, endpoint, and destructive impact, but lacks CVSS, CWE, precise role requirements, exploit telemetry, and patch details. Avoid expanding scope beyond WordPress uninstall plugin before 1.2.
Mitigation direction
- Check whether the WordPress uninstall plugin is installed.
- Confirm the installed plugin version is not before 1.2.
- Review the WordPress plugin page for current vendor guidance.
- Remove the plugin if it is unnecessary.
- Maintain restorable database backups for affected WordPress sites.
Validation and detection
- Inventory WordPress sites for the uninstall plugin.
- Record plugin versions and flag versions before 1.2.
- Review logs for requests to admin-ajax.php?action=uninstall.
- Confirm database backups restore successfully for exposed sites.
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.
CVE-2015-9332 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://wordpress.org/plugins/uninstall/#developersCVE reference · x_refsource_MISC
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.