Skip to main content

WP Support Plus EUVDEUVD-2026-42510

| CVE-2026-11875 MEDIUM
2026-07-09 WPScan GHSA-rwf6-mm98-7hfq
5.3
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Enumerate or obtain target user's email address
  2. Delivery
    Craft guest-session cookie with victim email value
  3. Exploit
    Send HTTP request with forged cookie to plugin endpoint
  4. Execution
    Plugin trusts cookie without verification
  5. Impact
    Read, reply to, or close victim's support tickets

Vulnerability Assessment

Exploitation Conditions

The WP Support Plus Responsive Ticket System plugin must be installed and active on a WordPress site with the guest (unauthenticated) ticket submission feature in use - this is the standard deployment mode for the plugin. The attacker must know or be able to enumerate the email address of the target ticket owner, as it is the sole identifier embedded in the forged cookie. No authentication, special network position, or privileged access is required (CVSS PR:N, AV:N, AC:L). Exploitation is limited to guest-session ticket data only - it does not affect authenticated WordPress user accounts, the WordPress admin panel, or server-side code. Sites that require all ticket submitters to register and authenticate as WordPress users are not exposed via this specific vector.

Impact

The NVD-assigned CVSS 5.3 Medium vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) captures the network-reachable, unauthenticated nature of the flaw but understates the integrity dimension: attackers can also reply to and close tickets, actions the C:L/I:N rating omits. My independent assessment adds I:L. EPSS of 0.14% at the 3rd percentile indicates very low observed exploitation probability in the broader population, despite SSVC classifying the attack as automatable - this tension is expected because automation feasibility does not equal widespread targeting of a niche plugin. No CISA KEV entry exists, meaning confirmed active exploitation has not been established; the POC is confirmed by WPScan and ENISA EUVD. Real-world impact is bounded: attackers must know or enumerate a target's email address, and the affected data is limited to support ticket content - not credentials, payment data, or server-side code execution. Priority should be proportional to the sensitivity of support ticket content in the specific deployment.

Exploit ScenarioDerived

An attacker who knows or enumerates a target user's email address constructs an HTTP request to the WordPress site with a crafted guest-session cookie bearing that email, requiring no credentials or prior interaction. The plugin accepts the cookie at face value, granting the attacker full read and write access to that user's support tickets - potentially exposing sensitive communications, allowing injection of misleading replies, or suppressing tickets by closing them. A publicly available proof-of-concept from WPScan lowers the technical bar for exploitation.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 09, 2026

Cookie forgery in WP Support Plus Responsive Ticket System (WordPress plugin ≤9.1.2) allows unauthenticated network attackers to impersonate any guest ticket owner by crafting an unsigned guest-session cookie containing the victim's email address, then reading, replying to, and closing that user's support tickets. The plugin fails to sign or verify its guest-session cookie, making the trust boundary between guest sessions trivially bypassable. A publicly available proof-of-concept exists per WPScan; EPSS is low at 0.14% (3rd percentile), suggesting limited observed exploitation despite automation feasibility confirmed by SSVC.

RemediationAI

No vendor-released patched version has been identified at time of analysis - the WPScan advisory at https://wpscan.com/vulnerability/1c69692e-5d0c-42cf-9b3d-b722f2ba4231/ should be consulted for updates. If no fix is available, the most effective compensating control is to deactivate the WP Support Plus plugin entirely and migrate to an actively maintained support ticket solution; this eliminates the attack surface with no functional trade-off if the plugin is otherwise unused. If disabling is not feasible, restrict access to the plugin's guest-ticket endpoints via WAF or server-level ACL rules so that only known or authenticated users can interact with the ticket system - note this removes the guest-submission feature. Additionally, audit existing guest ticket data for signs of unauthorized access by reviewing server access logs for anomalous cookie values targeting the plugin's session handler.

Affected VersionsENISA

WP Support Plus Responsive Ticket System 0 ≤9.1.2

Affected Packages

euvd wp_support_plus_responsive_ticket_system no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The WP Support Plus Responsive Ticket System is a WordPress plugin (CPE: cpe:2.3:a:unknown:wp_support_plus_responsive_ticket_system:*:*:*:*:*:*:*:*) that allows end users to submit and track support tickets as guests, identified by email address. The guest session is maintained via a cookie that the plugin sets client-side. The root cause is the absence of cryptographic signing or integrity verification on this cookie - analogous to CWE-565 (Reliance on Cookies without Validation and Integrity Checking) - meaning any client can fabricate a cookie value claiming to be any email address. No CWE is formally assigned in the NVD record. Because the plugin uses the email address from the cookie as a trust anchor for ticket ownership, an attacker who supplies an arbitrary email can fully impersonate that guest user. This pattern differs from session fixation or session hijacking: no existing session token is stolen - the attacker manufactures a valid-looking one from scratch.

Know when Wp Support Plus Responsive Ticket System gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (WPScan) PRIMARY 5.3 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
vuln.today AI 6.5 MEDIUM

Network-reachable with no prerequisites; integrity impact added (I:L) because attackers can reply to and close tickets beyond read access.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Lifecycle Timeline

3
CVSS changed
Jul 09, 2026 - 16:22 NVD
5.3 (None) 5.3 (MEDIUM)
CVE Published
Jul 09, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)
CVE Published
Jul 09, 2026 - 06:00 cve.org
MEDIUM 5.3

DescriptionCVE.org

The WP Support Plus Responsive Ticket System WordPress plugin through 9.1.2 does not sign or verify its guest-session cookie, allowing unauthenticated attackers to forge it and impersonate any ticket owner (identified by email address) to read, reply to, and close that person's support tickets.

Threat Intelligence Overview

EPSS Score
0.1%
Top 97% exploitable
Prevalence
Low
niche WordPress support ticket plugin, limited install base
Exploit
POC
Public exploit code exists
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy