Security readout for executives and security teams
Plain-English summary
This CVE describes a cross-site scripting issue in the WordPress Duplicate Post plugin before version 2.6. The public record provides little detail, so urgency depends on whether any business WordPress sites still run that old plugin version.
Executive priority
Prioritize as a targeted legacy WordPress hygiene issue, not a confirmed emergency. Escalate if internet-facing sites run Duplicate Post below 2.6 or cannot be upgraded promptly.
Technical view
The CVE record states that duplicate-post plugin versions before 2.6 for WordPress have XSS. The bundle does not provide CVSS, CWE, affected CPEs, attack vector, required privileges, or patch notes beyond the version boundary.
Likely exposure
Likely exposure is limited to WordPress installations using the Duplicate Post plugin below version 2.6. The source bundle does not identify specific CPEs, hosting environments, or affected configurations.
Exploitation context
CISA KEV is false, and the provided sources do not state active exploitation or public exploit availability. The exact XSS type and preconditions are not described in the bundle.
Researcher notes
Evidence is sparse. The CVE only asserts XSS before 2.6 and provides a WordPress plugin developer reference. Do not assume exploitability, payload behavior, or impacted roles without vendor or code-level confirmation.
Mitigation direction
- Inventory WordPress sites for the Duplicate Post plugin.
- Upgrade Duplicate Post to version 2.6 or later if installed.
- Check the WordPress plugin developer page for current vendor guidance.
- Remove the plugin where it is no longer needed.
Validation and detection
- Confirm each WordPress site's Duplicate Post plugin version.
- Flag any instance running below version 2.6.
- Review plugin change history around version 2.6.
- Check whether exposed sites still use unsupported legacy plugins.
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-2014-10378 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.
