dbcve.org
Wp Support Plus Responsive Ticket SystemWordPress extension · Wpsupportplus

CVE-2014-10390

CRITICAL · 9.1 CVSS v3.0 Published 2019-08-22
Fix available
A fix is available. Upgrade to 4.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The wp-support-plus-responsive-ticket-system plugin before 4.2 for WordPress has directory traversal.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The wp-support-plus-responsive-ticket-system WordPress plugin before version 4.2 contains a directory traversal vulnerability that allows attackers to access files outside the intended web root via manipulated path parameters, potentially exposing sensitive system files including WordPress configuration files.

MitigationUpgrade the wp-support-plus-responsive-ticket-system plugin to version 4.2 or later to obtain the patched code that properly validates and sanitizes file paths.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wp Support Plus Responsive Ticket SystemWordPress extension
Affected:< 4.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the plugin installation directory
    Check the WordPress plugins folder (wp-content/plugins/) for a folder named 'wp-support-plus-responsive-ticket-system', 'wp-support-plus', or similar variant. Use filesystem inspection or WordPress admin plugin list.
    Affected if The plugin folder exists in the WordPress installation
  2. Determine the installed plugin version
    Open the main plugin PHP file (usually plugin-name.php in the plugin folder) and locate the plugin header comment containing 'Version:' followed by a version number. Alternatively, check in WordPress admin under Plugins > Installed Plugins.
    Affected if The version number is found to be less than 4.2, or no version is displayed (indicating an old unversioned release)
  3. Verify the plugin is active
    Check WordPress admin under Plugins > Installed Plugins to confirm the plugin status shows as 'Active', or query the WordPress options database table for the active_plugins option.
    Affected if The plugin is activated and processing requests
  4. Identify vulnerable endpoints
    Examine HTTP requests to the plugin's AJAX handlers or ticket attachment/download features. Look for parameters that accept file paths (often named 'file', 'path', 'download', 'ticket_attachment', or similar). Common patterns include paths with '../' sequences or absolute paths outside the web root.
    Affected if The plugin accepts path parameters in HTTP requests without proper sanitization, allowing directory traversal sequences
  5. Test for directory traversal access
    If accessible endpoints accept path parameters, attempt a safe test request with a path like '../../../wp-config.php' or similar to see if the plugin returns file contents. Only perform this on authorized systems.
    Affected if The plugin returns contents of files outside the intended upload/attachment directory, confirming the vulnerability is exploitable

A user is affected if the wp-support-plus-responsive-ticket-system plugin is installed, active, and running a version lower than 4.2 that exposes path-handling functionality accessible via web requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.2 or later
Fixed in 4.2
Interim mitigation

Upgrade the wp-support-plus-responsive-ticket-system plugin to version 4.2 or later to obtain the patched code that properly validates and sanitizes file paths.

Recommended fix Moderate confidence

WP Support Plus Responsive Ticket System version 4.2 or later

  1. Backup your WordPress site before making any changes
  2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. Locate 'WP Support Plus Responsive Ticket System' in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 4.2 or later from the WordPress plugin repository
  5. After updating, verify the plugin version is 4.2 or higher under Plugins > Installed Plugins
  6. Test that the support ticket system functionality works correctly
Caveat Review plugin changelog for any breaking changes between your current version and 4.2; custom integrations may be affected

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wp Support Plus Responsive Ticket System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-10390 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-10390 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data