CVE-2025-54352Public exploitNetwork attack vector

Unpublished post-title disclosure via pingback oracle

Published Jul 21, 2025 · Updated Jul 21, 2025

Information disclosure in WordPress 3.5 through 6.8.2 allows remote attackers to infer unpublished post titles via XML-RPC pingbacks. In wp_xmlrpc_server::pingback_ping, fragment handling strips nonalphanumeric characters and queries titles across all post statuses instead of restricting the lookup to published posts. Unauthenticated access to xmlrpc.php and pingback.ping is sufficient; differential callbacks or the built-in one-second delay reveal whether each guessed substring occurs, disclosing titles but not post bodies.

CVSS severity3.7
Low
EPSS probability0.32%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Information disclosure in WordPress 3.5 through 6.8.2 allows remote attackers to infer unpublished post titles via XML-RPC pingbacks. In wp_xmlrpc_server::pingback_ping, fragment handling strips nonalphanumeric characters and queries titles across all post statuses instead of restricting the lookup to published posts. Unauthenticated access to xmlrpc.php and pingback.ping is sufficient; differential callbacks or the built-in one-second delay reveal whether each guessed substring occurs, disclosing titles but not post bodies.

The record

CVE
CVE-2025-54352
Published
Jul 21, 2025
Updated
Jul 21, 2025
Vendor
WordPress.org
Product
WordPress
Classifications
CWE-669
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jul 21, 2025CVE publishedPublication date reported by the CVE source.
  2. Jul 21, 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=3.5 <=6.8.2

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

WordPress.org · WordPressversion=3.5 <=6.8.2

Published CVSS scores

3.7MITRECVSS:3.1/AV:N/AC:H/PR:N/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 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-669Incorrect Resource Transfer Between Spheres

Public exploit references

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