CVE-2026-11875
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 · uneditedThe 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.
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 · high confidenceThe WP Support Plus Responsive Ticket System plugin through version 9.1.2 fails to implement cryptographic signing or verification on its guest-session cookie. This allows unauthenticated attackers to craft forged cookies by simply specifying any email address, enabling them to impersonate legitimate ticket owners and access, modify, or close associated support tickets.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins, locate 'WP Support Plus Responsive Ticket System', and note the version number displayed. Alternatively, check the plugin's main PHP file header for the 'Version' tag.Affected if The installed version is 9.1.2 or any earlier version (e.g., 9.1.1, 9.0.5, etc.).
-
Confirm guest ticket submission is enabledNavigate to WP Support Plus settings (typically under Support Plus > Settings > General Settings) and check whether the 'Allow guest ticket' or 'Guest Ticket' option is enabled, which permits ticket creation without WordPress user authentication.Affected if Guest ticket functionality is enabled, allowing unauthenticated users to create tickets using only an email address.
-
Inspect the guest-session cookie mechanismCreate a test guest ticket (or use browser dev tools) to examine the cookie set by the plugin. Look for a cookie named something like 'guest_session', 'wpsp_cookie', or similar that contains an email address or user identifier in plain or weakly obfuscated form, without a verifiable HMAC signature component.Affected if The cookie contains only an email address or user ID without a cryptographic signature or verification token, indicating the vulnerable implementation.
You are affected if the plugin version is 9.1.2 or lower AND guest ticket submission is enabled, which allows attackers to forge session cookies and impersonate ticket owners.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to a patched version of the plugin that implements proper HMAC-based cookie signing and email validation, or implement additional server-side session validation mechanisms.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11875 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-11875 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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