Security readout for executives and security teams
Plain-English summary
This CVE covers a directory traversal flaw in the wp-support-plus-responsive-ticket-system WordPress plugin before version 4.2. In plain terms, an affected site may expose files outside the intended plugin area. The provided sources do not include impact details, CVSS scoring, exploit evidence, or remediation text beyond the affected version boundary.
Executive priority
Prioritize discovery first. Business urgency depends on whether the plugin is present and below 4.2, because the provided sources do not quantify severity or confirm exploitation.
Technical view
The vulnerability is described only as directory traversal in the WordPress wp-support-plus-responsive-ticket-system plugin before 4.2. The source bundle does not specify vulnerable parameters, authentication requirements, readable file scope, affected WordPress versions, or whether exploitation is practical remotely.
Likely exposure
Exposure is limited to WordPress sites running the wp-support-plus-responsive-ticket-system plugin before 4.2. The provided affected-product metadata is incomplete, so organizations should verify plugin presence and exact installed versions rather than relying on CPE matching.
Exploitation context
The source bundle states this is not in KEV and provides no cited evidence of active exploitation, public exploit use, or attack volume. Treat exploitation status as unconfirmed, not absent.
Researcher notes
Evidence is sparse. The CVE description gives the vulnerability class and version boundary only. No CVSS, CWE, exploitability conditions, vulnerable endpoint, or remediation procedure is provided in the bundle.
Mitigation direction
- Inventory WordPress sites for this plugin and record installed versions.
- Upgrade affected installations to 4.2 or later where vendor guidance supports it.
- If upgrade is unavailable, follow vendor guidance or remove the plugin.
- Restrict administrative access while remediation is assessed.
- Monitor web logs for suspicious file-access patterns.
Validation and detection
- Confirm whether the plugin is installed on each WordPress site.
- Verify installed plugin versions are not earlier than 4.2.
- Check the CVE record and WordPress plugin page for vendor updates.
- Review logs for anomalous requests involving unexpected file paths.
- Document sites where plugin status or version cannot be confirmed.
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.
File access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell 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-10390 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.