WP Discourse <= 2.5.9 - Authenticated (Author+) Information Exposure
Strategic Overview
- Status
- Patched in 2.6.0
- Affected Plugin
- WP Discourse
- Affected Version
<= 2.5.9- CVSS
- 4.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2025-11983
At a glance
CVE-2025-11983 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the WP Discourse WordPress plugin, affecting versions <= 2.5.9. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Author level or above. The issue is fixed in version 2.6.0; sites on affected versions should update now. Disclosed October 2025, reported by Jonas Benjamin Friedli.
Vulnerability Overview
The WP Discourse plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 2.5.9. This is due to the plugin unconditionally sending Discourse API credentials (Api-Key and Api-Username headers) to any host specified in a post's discourse_permalink custom field during comment synchronization. This makes it possible for authenticated attackers, with author-level access and above, to exfiltrate sensitive Discourse API credentials to attacker-controlled servers, as well as query internal services and potentially perform further attacks.
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 WP Discourse <= 2.5.9 takes an account at Author 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 WP Discourse the fix is 2.6.0: builds <= 2.5.9 are affected, anything from 2.6.0 onward is not.
Remediation
Update to version 2.6.0, or a newer patched version
How does WordSec protect against this?
The fix is the thing that ends this: WP Discourse 2.6.0 closes this, and updating the plugin is the step that ends it.
- Alerts
External References
Related records
Other vulnerabilities in WP Discourse
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C