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

CVE-2016-10930

CRITICAL · 9.8 CVSS v3.0 Published 2019-08-22
Fix available
A fix is available. Upgrade to 7.1.0 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 7.1.0 for WordPress has insecure direct object reference via a ticket number.

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 plugin before version 7.1.0 contains an Insecure Direct Object Reference (IDOR) vulnerability that allows attackers to access support tickets by manipulating ticket numbers without proper authorization validation. This enables unauthorized users to view, modify, or delete tickets belonging to other users.

MitigationUpdate the wp-support-plus-responsive-ticket-system plugin to version 7.1.0 or later to remediate the IDOR vulnerability. Additionally, audit user access controls and implement proper authorization checks on all ticket operations.

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:< 7.1.0

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
High

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

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 wp-support-plus-responsive-ticket-system plugin files
    Access your WordPress installation via FTP or file manager, then navigate to /wp-content/plugins/ and look for a folder named 'wp-support-plus-responsive-ticket-system' or similar variant containing 'wpsupportplus'
    Affected if The plugin folder exists in the plugins directory
  2. Determine the installed plugin version
    Open the main plugin PHP file (typically named wpsupportplus.php or similar) and locate the version comment in the plugin header, or check the 'Version' field in WordPress Admin > Plugins > Plugin Editor
    Affected if The version number displayed is less than 7.1.0 (for example, 7.0.x, 6.x, or earlier)
  3. Verify the ticket system functionality is active
    Log into WordPress Admin and navigate to the plugin settings or check if ticket-related menu items exist (such as 'Support Tickets', 'Support Plus', or similar) indicating the plugin is enabled and functional
    Affected if The ticket system features are accessible and operational in the WordPress admin panel

You are affected if the wp-support-plus-responsive-ticket-system plugin is installed and its version is below 7.1.0, with the ticket functionality enabled.

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 7.1.0 or later
Fixed in 7.1.0
Interim mitigation

Update the wp-support-plus-responsive-ticket-system plugin to version 7.1.0 or later to remediate the IDOR vulnerability. Additionally, audit user access controls and implement proper authorization checks on all ticket operations.

Recommended fix Moderate confidence

7.1.0 or later

  1. Backup your WordPress site and database 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. Verify current version is below 7.1.0 (if version is 7.1.0 or higher, you are not affected)
  5. Click 'Update Now' to update to the latest version, or manually download version 7.1.0 or higher from wordpress.org plugin repository
  6. After updating, clear any caching plugins and verify the plugin is functioning correctly
  7. Test that ticket access controls are working properly - ensure users can only access tickets they are authorized to view

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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-10930 — 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-2016-10930 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