Security readout for executives and security teams
Plain-English summary
This CVE concerns a JavaScript injection issue in the wp-support-plus-responsive-ticket-system WordPress plugin before version 4.1. The public bundle does not provide CVSS, CWE, exploit status, or impact details, so urgency depends on whether affected plugin versions remain installed on public sites.
Executive priority
Treat this as an inventory-driven cleanup item unless affected versions are internet-facing or used by privileged staff. The main business risk is possible script execution in WordPress support workflows, but the public evidence does not support a higher rating.
Technical view
The source describes JavaScript injection in wp-support-plus-responsive-ticket-system before 4.1. It does not specify the injection vector, authentication requirement, affected parameters, or whether exploitation is stored, reflected, or admin-only. KEV is false in the provided bundle.
Likely exposure
Exposure is likely limited to WordPress sites running wp-support-plus-responsive-ticket-system versions before 4.1. The bundle lists generic affected metadata as unavailable, so confirm from installed plugin inventory rather than product assumptions.
Exploitation context
No active exploitation evidence is provided, and the CVE is not marked KEV in the bundle. Public details are sparse, so treat exploitability and business impact as unconfirmed until vendor records or local testing clarify reachability.
Researcher notes
The bundle lacks CVSS, CWE, proof details, fixed-version text beyond “before 4.1,” and exploit telemetry. Avoid assuming XSS subtype or authentication context. Validate exposure by installed plugin version and consult vendor/plugin history for remediation confirmation.
Mitigation direction
- Identify all WordPress sites using wp-support-plus-responsive-ticket-system.
- Remove or disable plugin versions before 4.1 if no update is available.
- Check the WordPress plugin developer page for vendor-supported upgrade guidance.
- Prioritize internet-facing sites and administrator-facing support portals first.
Validation and detection
- Review WordPress plugin inventory for wp-support-plus-responsive-ticket-system versions before 4.1.
- Confirm whether the plugin is active, inactive, or removed on each site.
- Check security monitoring for suspicious script injection indicators on affected sites.
- Document whether each instance was upgraded, disabled, or accepted as risk.
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-10391 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-support-plus-responsive-ticket-system/#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.