WPC Admin Columns <= 2.3.3 - Information Exposure to Authenticated (Subscriber+) Arbitrary User/Post/Term Meta Disclosure
Strategic Overview
- Status
- Patched in 2.3.4
- Affected Plugin
- WPC Admin Columns
- Affected Version
<= 2.3.3- CVSS
- 4.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2026-18943
At a glance
CVE-2026-18943 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the WPC Admin Columns WordPress plugin, affecting versions <= 2.3.3. 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 2.3.4; sites on affected versions should update now. Disclosed August 2026, reported by Farid Narimanov.
Vulnerability Overview
The WPC Admin Columns plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 2.3.3. This is due to missing capability checks before returning term, user, and post meta via AJAX endpoints accessible to any authenticated user. This makes it possible for authenticated attackers, with subscriber-level access and above, to read arbitrary term, user, and post meta values belonging to any object by exploiting missing capability checks on meta retrieval AJAX handlers.
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-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in WPC Admin Columns <= 2.3.3 takes an account at Subscriber level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For WPC Admin Columns the fix is 2.3.4: builds <= 2.3.3 are affected, anything from 2.3.4 onward is not.
Remediation
Update to version 2.3.4, or a newer patched version
How does WordSec protect against this?
The fix is the thing that ends this: WPC Admin Columns 2.3.4 closes this, and updating the plugin is the step that ends it.
- Alerts
External References
Related records
Other vulnerabilities in WPC Admin Columns
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C