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

CVE-2019-15331

MEDIUM · 6.1 CVSS v3.0 Published 2019-08-22
Fix available
A fix is available. Upgrade to 9.1.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 9.1.2 for WordPress has HTML injection.

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 9.1.2 contains an HTML injection vulnerability. This allows attackers to inject malicious HTML markup into support ticket fields, which can result in stored cross-site scripting (XSS) when staff or other users view the affected tickets in the WordPress admin dashboard.

MitigationUpgrade the wp-support-plus-responsive-ticket-system plugin to version 9.1.2 or later to obtain the patch that addresses the HTML injection vulnerability.

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:< 9.1.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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Check installed plugin version
    Navigate to WordPress Admin > Plugins > Installed Plugins. Locate 'Wp Support Plus Responsive Ticket System' and read the version number displayed below the plugin name.
    Affected if The version shown is lower than 9.1.2 (for example, 9.1.1, 9.1.0, or earlier).
  2. Verify plugin is active
    In the same plugins list, confirm the plugin has an 'Active' status indicator (typically a green 'Active' link or similar).
    Affected if The plugin is active and the version is below 9.1.2.
  3. Confirm ticket submission functionality exists
    Check if the plugin has created any public-facing ticket submission forms or if any tickets have been submitted in the system. Access WordPress Admin > Support Plus or similar menu item the plugin provides to view existing tickets.
    Affected if The plugin is active, version is below 9.1.2, and ticket submission or viewing functionality is present in the environment.

You are affected if the wp-support-plus-responsive-ticket-system plugin is installed, active, and running at a version lower than 9.1.2, with ticket functionality available for use.

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.

From vendor data
Upgrade available Upgrade to 9.1.2 or later
Fixed in 9.1.2
Interim mitigation

Upgrade the wp-support-plus-responsive-ticket-system plugin to version 9.1.2 or later to obtain the patch that addresses the HTML injection vulnerability.

Fix this in Wp Support Plus Responsive Ticket System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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