CVE-2025-11983Network attack vectorHinoki check available

Credential theft via unchecked comment-sync destination

Published Nov 1, 2025 · Updated Nov 1, 2025

Information exposure in Discourse WP Discourse 2.5.9 and earlier allows remote authenticated users to steal Discourse API credentials. The comment-sync path reads a post's discourse_permalink custom field as the request destination and forwards Api-Key and Api-Username headers without validating its host. Author-level access is sufficient to point synchronization at an attacker-controlled server, exposing the credentials and enabling requests to internal services.

CVSS severity4.3
Medium
EPSS probability0.25%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Information exposure in Discourse WP Discourse 2.5.9 and earlier allows remote authenticated users to steal Discourse API credentials. The comment-sync path reads a post's discourse_permalink custom field as the request destination and forwards Api-Key and Api-Username headers without validating its host. Author-level access is sufficient to point synchronization at an attacker-controlled server, exposing the credentials and enabling requests to internal services.

The record

CVE
CVE-2025-11983
Published
Nov 1, 2025
Updated
Nov 1, 2025
Vendor
Discourse
Product
WP Discourse
Classifications
CWE-200, T1190
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Nov 1, 2025CVE publishedPublication date reported by the CVE source.
  2. Nov 1, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=* <=2.5.9

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Discourse · WP Discourseversion=* <=2.5.9

Published CVSS scores

4.3WordfenceCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-200Exposure of Sensitive Information to an Unauthorized Actor
T1190Exploit Public-Facing Application

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo