CVE-2026-14183

Classified Listing <= 5.3.8 - Insecure Direct Object Reference to Authenticated (Subscriber+) Receipt Disclosure

2026-06-30 00:00
PO-WEI TING (Dinlon5566) , Open Information Security Inc.

Strategic Overview

Status
Patched in 5.3.9
Affected Plugin
Classified Listing – AI-Powered Classified ads & Business Directory
Affected Version
<= 5.3.8
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-14183
View all Classified Listing – AI-Powered Classified ads & Business Directory vulnerabilities

At a glance

CVE-2026-14183 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Classified Listing WordPress plugin, affecting versions <= 5.3.8. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 5.3.9; sites on affected versions should update now. Disclosed June 2026, reported by PO-WEI TING (Dinlon5566) , Open Information Security Inc..

Vulnerability Overview

The Classified Listing – AI-Powered Classified ads & Business Directory plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 5.3.8 due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Subscriber-level access and above, to read other user's receipts.

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 Classified Listing <= 5.3.8 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 Classified Listing the fix is 5.3.9: builds <= 5.3.8 are affected, anything from 5.3.9 onward is not.

Remediation

Update to version 5.3.9, 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: Classified Listing 5.3.9 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-14183https://www.wordfence.com/threat-intel/vulnerabilities/id/51560b6e-e926-4c3e-aa43-d604e7239a91https://nvd.nist.gov/vuln/detail/CVE-2026-14183

Related records

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