Security readout for executives and security teams
Plain-English summary
CVE-2014-10376 is a SQL injection issue in the WordPress i-recommend-this plugin before version 3.7.3. The provided sources do not include severity scoring, affected parameters, or exploitation evidence. Treat exposure as a WordPress plugin inventory and patching issue, especially for public sites.
Executive priority
Prioritize identification and update on internet-facing WordPress sites. This is not source-confirmed as actively exploited, but SQL injection is a serious class when reachable.
Technical view
The CVE record states that i-recommend-this before 3.7.3 for WordPress has SQL injection. No CVSS, CWE, authentication requirement, vulnerable endpoint, or proof of exploitability is provided in the source bundle, so technical impact cannot be precisely scored from these sources alone.
Likely exposure
Likely limited to WordPress sites running the i-recommend-this plugin below 3.7.3. Exposure cannot be confirmed without checking plugin inventory and deployed versions.
Exploitation context
The bundle marks KEV as false, and no provided source states active exploitation. SQL injection can affect database confidentiality or integrity, but this CVE's reachable attack surface is not described.
Researcher notes
The public record is sparse. Key missing items include vulnerable parameter, endpoint, authentication context, fixed commit, CVSS vector, and exploitation evidence. Avoid assuming exploitability beyond the stated SQL injection in versions before 3.7.3.
Mitigation direction
- Inventory WordPress sites for the i-recommend-this plugin.
- Upgrade the plugin to version 3.7.3 or later where still used.
- Remove the plugin if it is unnecessary or unsupported.
- Check WordPress plugin guidance for any additional vendor notes.
Validation and detection
- Confirm installed plugin versions across WordPress environments.
- Verify no site is running i-recommend-this below 3.7.3.
- Review web logs for suspicious requests to plugin-related paths.
- Document any exposed legacy sites needing remediation.
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-2014-10376 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/i-recommend-this/#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.