CVE-2025-12681Network attack vector

Unauthenticated comment-author data disclosure via unfiltered AJAX response

Published Nov 13, 2025 · Updated Nov 13, 2025

Sensitive information exposure in Comment Edit Core 3.1.0 and earlier allows remote attackers to read comment authors' private data. The ajax_get_comment handler accepts an attacker-selected comment identifier and returns the complete WordPress comment object without restricting its response to public fields. No authentication or user interaction is required, and exposed fields include user IDs, IP addresses, and email addresses.

CVSS severity5.3
Medium
EPSS probability0.29%
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

Sensitive information exposure in Comment Edit Core 3.1.0 and earlier allows remote attackers to read comment authors' private data. The ajax_get_comment handler accepts an attacker-selected comment identifier and returns the complete WordPress comment object without restricting its response to public fields. No authentication or user interaction is required, and exposed fields include user IDs, IP addresses, and email addresses.

The record

CVE
CVE-2025-12681
Published
Nov 13, 2025
Updated
Nov 13, 2025
Vendor
Ronald Huereca
Product
Comment Edit Core
Classifications
CWE-200, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Nov 13, 2025CVE publishedPublication date reported by the CVE source.
  2. Nov 13, 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.1.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Ronald Huereca · Comment Edit Coreversion=* <=3.1.0

Published CVSS scores

5.3WordfenceCVSS:3.1/AV:N/AC:L/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 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
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