CVE-2026-11801

WPAdverts <= 2.3.2 - Missing Authorization to Unauthenticated Sensitive Information Disclosure via classifieds-types REST Endpoint

2026-08-17 13:29
Deva Parekh

Strategic Overview

Status
Patched in 2.3.3
Affected Plugin
WPAdverts – Classifieds Plugin
Affected Version
<= 2.3.2
CVSS
7.5High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-11801
View all WPAdverts – Classifieds Plugin vulnerabilities

At a glance

CVE-2026-11801 is a high-severity Missing Authorization vulnerability in the WPAdverts WordPress plugin, affecting versions <= 2.3.2. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 2.3.3; sites on affected versions should update now. Disclosed August 2026, reported by Deva Parekh.

Vulnerability Overview

The WPAdverts – Classifieds Plugin plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.3.2. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to retrieve internal site configuration data exposed by the classifieds-types REST endpoint, including registered post types, labels, associated taxonomies, form scheme metadata, contact options, and custom field meta keys.

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.

CWE-862: Missing Authorization

Reaching this weakness in WPAdverts <= 2.3.2 takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WPAdverts the fix is 2.3.3: builds <= 2.3.2 are affected, anything from 2.3.3 onward is not.

Remediation

Update to version 2.3.3, or a newer patched version

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. None of that substitutes for the fix: WPAdverts 2.3.3 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-11801https://www.wordfence.com/threat-intel/vulnerabilities/id/37bb8d68-dd87-437a-80e5-e99e93dc55b6https://nvd.nist.gov/vuln/detail/CVE-2026-11801

Related records

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