Security readout for executives and security teams
Plain-English summary
A WordPress plugin called duplicate-post had a SQL injection issue in versions before 2.6. The public bundle gives very little detail, so business risk depends on whether the plugin is installed and exposed on your WordPress sites.
Executive priority
Treat this as an exposure-verification item. Prioritize any internet-facing WordPress site running the plugin before 2.6, but avoid emergency assumptions without local evidence.
Technical view
CVE-2014-10379 describes SQL injection in the duplicate-post WordPress plugin before version 2.6. The sources do not provide CVSS, CWE, vulnerable endpoint, required privileges, affected parameter, exploit details, or impact scope.
Likely exposure
Exposure is limited to WordPress sites running the duplicate-post plugin before 2.6. The provided affected-product metadata is incomplete and lists no CPEs.
Exploitation context
The bundle does not show active exploitation. It marks KEV as false and provides no cited exploit report, proof-of-concept status, or attack preconditions.
Researcher notes
Evidence is sparse. The useful source-grounded facts are the plugin name, version boundary, vulnerability class, publication/update dates, and absence of KEV status in the supplied bundle.
Mitigation direction
- Inventory WordPress sites for the duplicate-post plugin.
- If installed below 2.6, update to 2.6 or a current vendor-supported release.
- Check vendor plugin guidance for any additional remediation notes.
- Review database and WordPress logs for suspicious plugin-related activity.
Validation and detection
- Confirm the installed duplicate-post plugin version on each WordPress site.
- Verify no site remains on a version before 2.6.
- Document whether the plugin is internet-facing or restricted to administrators.
- Record compensating controls if immediate update is not possible.
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-10379 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/duplicate-post/#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.