Wp Discourse
Approved changes feed: RSS · Atom
cpe:2.3:a:scossar:wp_discourse:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Scossar (7bce07c0-3323-5c63-8e34-6b3b43e65d62) |
|---|---|
| Product | Wp Discourse (906aff25-f32f-59e8-9ba5-6cd52924f2c2) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-11983 |
vulnerable | 2026-06-08 07:04:29.507751 |
WP Discourse <= 2.5.9 - Authenticated (Author+) Information Exposure
MEDIUM (4.3)
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.
Published: 2025-11-01T05:40:23.063Z
Updated: 2026-04-08T16:58:56.374Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.