Security readout for executives and security teams
Plain-English summary
CVE-2015-9330 affects older versions of the wp-all-import WordPress plugin. Versions before 3.2.5 are described as having blind SQL injection, which can put site database data at risk. The source bundle does not provide severity scoring, proof of exploitation, or technical detail.
Executive priority
Prioritize remediation if wp-all-import is installed, especially on public or business-critical WordPress sites. The available evidence supports a real vulnerable version range but does not support claims of active exploitation or quantified severity.
Technical view
The CVE record states that wp-all-import before 3.2.5 contains a blind SQL injection vulnerability. No CVSS vector, CWE, endpoint, parameter, authentication requirement, or vendor mitigation details are included in the supplied evidence beyond the affected version boundary.
Likely exposure
Exposure is limited to WordPress sites running the wp-all-import plugin below version 3.2.5. Internet-facing WordPress administration or import workflows may increase business risk, but the sources do not define the vulnerable path or required privileges.
Exploitation context
The supplied bundle says this is blind SQL injection, but KEV is false and no cited source confirms active exploitation. No exploit maturity, public exploit detail, or attacker preconditions are provided.
Researcher notes
The record is sparse. Useful missing facts include vulnerable request surface, affected parameters, authentication requirement, CVSS, CWE classification, and patch notes. Treat validation as version-based unless stronger vendor or advisory evidence is obtained.
Mitigation direction
- Inventory WordPress sites for the wp-all-import plugin.
- Upgrade wp-all-import to version 3.2.5 or later where present.
- Check current vendor guidance before applying production changes.
- Restrict administrative access to WordPress where operationally possible.
- Back up the site and database before plugin changes.
Validation and detection
- Confirm each WordPress site's installed wp-all-import version.
- Verify no instance remains below version 3.2.5.
- Review plugin changelog or vendor page for current security notes.
- Review relevant web and application logs for unexplained import-related activity.
- Document sites where the plugin is absent or already updated.
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.
Database behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2015-9330 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/wp-all-import/#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.