# CVE-2025-11983: WP Discourse <= 2.5.9 - Authenticated (Author+) Information Exposure

> Authenticated attackers can exfiltrate Discourse API credentials and query internal services by manipulating post permalink fields in the WP Discourse plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Nov 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-95h8-w3mv-h4hq

## What is CVE-2025-11983?

CVE-2025-11983 is a medium-severity vulnerability in scossar WP Discourse, published on 1 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-11983?


## How do I fix CVE-2025-11983?

No fix has been published for CVE-2025-11983 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-11983 being exploited?

There is no known exploitation of CVE-2025-11983 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-11983 and fix it if it is affected.

What it is: CVE-2025-11983 is a medium-severity vulnerability in scossar WP Discourse, published on 1 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-11983 in the wild and no public exploit code.

Affected product: scossar WP Discourse. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-11983/ (Markdown: https://insights.sbomify.com/CVE-2025-11983/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-11983
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-11983
- OSV: https://osv.dev/vulnerability/CVE-2025-11983

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-11983/
Summaries are generated and may contain mistakes; the official description above is the record.