CVE-2025-11377

List category posts <= 0.92.0 - Authenticated (Contributor+) Information Exposure

Strategic Overview

Status
Patched in 0.93.0
Affected Plugin
List category posts
Affected Version
<= 0.92.0
CVSS
4.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2025-11377
View all List category posts vulnerabilities

At a glance

CVE-2025-11377 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the List category posts WordPress plugin, affecting versions <= 0.92.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 0.93.0; sites on affected versions should update now. Disclosed October 2025, reported by Athiwat Tiprasaharn (Jitlada).

Vulnerability Overview

The List category posts plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 0.92.0 via the 'catlist' shortcode due to insufficient restrictions on which posts can be included. This makes it possible for authenticated attackers, with contributor-level access and above, to extract data from password protected, private, or draft posts that they should not have access to.

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

List category posts <= 0.92.0 carries this weakness at catlist, and reaching it takes an account at Contributor 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 List category posts the fix is 0.93.0: builds <= 0.92.0 are affected, anything from 0.93.0 onward is not.

Remediation

Update to version 0.93.0, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: List category posts 0.93.0 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

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