CVE-2025-11983: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in scossar WP Discourse
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.
AI Analysis
Technical Summary
CVE-2025-11983 is an information exposure vulnerability (CWE-200) in the WP Discourse WordPress plugin, affecting all versions up to and including 2.5.9. The plugin sends Discourse API credentials (Api-Key and Api-Username headers) to any host specified in a post's discourse_permalink custom field during comment synchronization without validation. This allows authenticated users with author-level privileges or higher to exfiltrate sensitive API credentials to attacker-controlled servers and potentially query internal services, increasing the risk of further exploitation. The vulnerability is network exploitable with low attack complexity and no user interaction required, but requires authenticated author-level access.
Potential Impact
The vulnerability allows exposure of sensitive Discourse API credentials to unauthorized actors with author-level access or higher. This can lead to credential exfiltration to attacker-controlled servers, enabling unauthorized access to Discourse APIs. The impact is limited to confidentiality loss without direct integrity or availability impact. There are no known exploits in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict author-level access to trusted users only and monitor for suspicious activity related to API credential exposure. Avoid using untrusted or user-supplied discourse_permalink values. Follow vendor updates closely for any released patches or official mitigations.
CVE-2025-11983: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in scossar WP Discourse
Description
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2025-11983 is an information exposure vulnerability (CWE-200) in the WP Discourse WordPress plugin, affecting all versions up to and including 2.5.9. The plugin sends Discourse API credentials (Api-Key and Api-Username headers) to any host specified in a post's discourse_permalink custom field during comment synchronization without validation. This allows authenticated users with author-level privileges or higher to exfiltrate sensitive API credentials to attacker-controlled servers and potentially query internal services, increasing the risk of further exploitation. The vulnerability is network exploitable with low attack complexity and no user interaction required, but requires authenticated author-level access.
Potential Impact
The vulnerability allows exposure of sensitive Discourse API credentials to unauthorized actors with author-level access or higher. This can lead to credential exfiltration to attacker-controlled servers, enabling unauthorized access to Discourse APIs. The impact is limited to confidentiality loss without direct integrity or availability impact. There are no known exploits in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict author-level access to trusted users only and monitor for suspicious activity related to API credential exposure. Avoid using untrusted or user-supplied discourse_permalink values. Follow vendor updates closely for any released patches or official mitigations.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-10-20T18:28:48.760Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69059f2e1e4a8d05dce595cd
Added to database: 11/1/2025, 5:48:30 AM
Last enriched: 4/9/2026, 4:01:04 PM
Last updated: 5/10/2026, 6:38:35 AM
Views: 160
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.