CVE-2025-30777

Support Genix <= 1.4.11 - Authenticated (Subscriber+) Insecure Direct Object Reference

2025-03-27 00:00
astra.r3verii

Strategic Overview

Status
Patched in 1.4.12
Affected Version
<= 1.4.11
CVSS
5.4Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2025-30777
View all Support Genix – Helpdesk, AI Chatbot, Knowledge Base & Customer Support Ticketing System vulnerabilities

At a glance

CVE-2025-30777 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Support Genix WordPress plugin, affecting versions <= 1.4.11. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.4.12; sites on affected versions should update now. Disclosed March 2025, reported by astra.r3verii.

Vulnerability Overview

The Support Genix – Helpdesk & Customer Support Ticket System plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.4.11 due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Subscriber-level access and above, to perform an unauthorized action.

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 interaction from a victim user.

CWE-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in Support Genix <= 1.4.11 takes an account at Subscriber level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Support Genix the fix is 1.4.12: builds <= 1.4.11 are affected, anything from 1.4.12 onward is not.

Remediation

Update to version 1.4.12, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Support Genix 1.4.12 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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