Security readout for executives and security teams
Plain-English summary
This is a SQL injection flaw in the WordPress 404like plugin. A remote unauthenticated attacker could potentially interfere with the site database through the plugin’s page-checking logic. The bundle does not show active exploitation, but the network-accessible and no-authentication characteristics make exposed WordPress sites a meaningful business risk.
Executive priority
Prioritize remediation for internet-facing WordPress sites because this is a database-impacting flaw requiring no authentication. The highest-value action is confirming whether the obsolete 404like plugin is present. If present, upgrade, verify the patch, or remove the plugin.
Technical view
CVE-2012-10009 is CWE-89 in 404like Plugin 404Like.php, function checkPage, through the searchWord argument. CVSS v2 is 7.5: AV:N/AC:L/Au:N/C:P/I:P/A:P. The bundle cites a patch commit and release 1.0.2, but also lists 1.0.2 as affected, so version status should be verified carefully.
Likely exposure
Exposure is likely limited to WordPress installations running the 404like plugin. The bundle lists versions 1.0.0, 1.0.1, and 1.0.2, while also saying 1.0.2 fixes the issue. Internet-facing WordPress sites running this plugin are the primary concern.
Exploitation context
The CVSS vector indicates remote, low-complexity exploitation without authentication. The source bundle marks KEV as false and provides no cited evidence of active exploitation. Treat public exploitability as plausible from the vulnerability class, but do not claim in-the-wild use from these sources.
Researcher notes
The main uncertainty is versioning: the description says upgrading to 1.0.2 addresses the issue, while the affected list includes 1.0.2. Researchers should verify the patch diff and installed code state rather than relying only on version labels.
Mitigation direction
- Inventory WordPress sites for the 404like plugin and exact installed version.
- Upgrade to the cited fixed 1.0.2 release or current vendor-recommended package.
- If version status is unclear, disable or remove the plugin until fixed code is verified.
- Review the cited patch before accepting 1.0.2 as remediated.
- Monitor WordPress and database logs for suspicious plugin-related requests.
Validation and detection
- Confirm whether 404like is installed on any managed WordPress site.
- Compare installed plugin code against commit 2c4b589d27554910ab1fd104ddbec9331b540f7f.
- Verify the running package matches the trusted fixed release artifact.
- Check vulnerability management data for assets exposing affected WordPress sites publicly.
- Document any compensating controls if immediate upgrade or removal is delayed.
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-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. 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 lookupDatabase 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-2012-10009 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
- High
- CVSS
- 7.5 (2.0)
- Known Exploited
- No
- Published
Vector: AV:N/AC:L/Au:N/C:P/I:P/A:P
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 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.
AV:N/AC:L/Au:N/C:P/I:P/A:P106.4Primary CVE scoreVulnerability scoring details
Base CVSS 2.0 score
7.5HighVector: AV:N/AC:L/Au:N/C:P/I:P/A:P
Source materials
- CVE List V5 sourceCVE List V5
- https://vuldb.com/?id.223404CVE reference · vdb-entry, technical-description
- https://vuldb.com/?ctiid.223404CVE reference · signature, permissions-required
- https://github.com/wp-plugins/404like/commit/2c4b589d27554910ab1fd104ddbec9331b540f7fCVE reference · patch
- https://github.com/wp-plugins/404like/releases/tag/1.0.2CVE reference · patch
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.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.