CVE-2025-69179

Support Ticket Management System <= 1.9 - Unauthenticated Privilege Escalation

2026-05-28 00:00
Phat RiO

Strategic Overview

Status
Unpatched
Affected Version
<= 1.9
CVSS
9.8Critical
Weakness type
CWE-266 · Incorrect Privilege Assignment
CVE
CVE-2025-69179
View all Support Ticket Management System for WordPress vulnerabilities

At a glance

CVE-2025-69179 is a critical-severity Incorrect Privilege Assignment vulnerability in the Support Ticket Management System for WordPress WordPress plugin, affecting versions <= 1.9. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed May 2026, reported by Phat RiO.

Vulnerability Overview

The Support Ticket Management System for WordPress plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.9. This makes it possible for unauthenticated attackers to elevate their privileges.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-266: Incorrect Privilege Assignment

A product incorrectly assigns a privilege to a particular actor, creating an unintended sphere of control for that actor.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C