Security readout for executives and security teams
Plain-English summary
A remote, unauthenticated attacker may place malicious browser code into Debug Log Manager content. That code can run when someone later views the affected page, potentially exposing information or allowing limited actions in that viewer’s WordPress session. The supplied assessment scores it 7.2, High.
Executive priority
Treat as a high-priority WordPress remediation where the plugin is installed, especially on externally reachable or privileged sites. Promptly inventory, verify vendor guidance, and update or disable. There is no supplied evidence of active exploitation, so this is urgent risk reduction rather than a confirmed incident.
Technical view
Debug Log Manager through 2.3.4 reportedly fails to sanitize untrusted debug-log input and escape it during auto-refresh rendering, creating stored cross-site scripting (CWE-79). The CVSS 3.1 vector is network-accessible, low-complexity, unauthenticated, scope-changing, with low confidentiality and integrity impact and no stated availability impact.
Likely exposure
Likely exposure is limited to WordPress installations running Debug Log Manager version 2.3.4 or earlier. Risk is greatest where the vulnerable auto-refresh log view is used. The bundle’s structured affected-version entry is inconsistent with its description, so confirm applicability against the vendor record.
Exploitation context
The source bundle does not identify this CVE as CISA KEV and provides no evidence of active exploitation. Exploitation is nevertheless described as remotely reachable without authentication. Successful impact depends on stored attacker-controlled content being rendered in a user’s browser.
Researcher notes
CVE-2025-32613 is identified as a duplicate. The bundle links Wordfence and WordPress changeset records but does not explicitly name a fixed release. Its structured affected entry lists version “0” with default status unaffected, conflicting with the narrative’s through-2.3.4 range; validate authoritative vendor metadata before final scoping.
Mitigation direction
- Inventory WordPress sites and identify installed Debug Log Manager versions.
- Check the vendor and WordPress plugin guidance for a confirmed fixed release, then update promptly.
- If no fixed release is confirmed, disable or remove the plugin until guidance is available.
- Restrict access to debugging interfaces as defense in depth; this does not correct unsafe rendering.
- Review and safely remove confirmed malicious stored log content after preserving necessary evidence.
Validation and detection
- Confirm the plugin version on every WordPress installation, including inactive copies.
- Verify the installed release against the vendor’s confirmed affected and fixed version information.
- Inspect debug logs as plain text for unexpected script-like or HTML content; avoid rendering it.
- Confirm untrusted log content is encoded during display and auto-refresh after remediation.
- Review relevant access and administrative logs for suspicious activity around debug-log viewing.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-3809 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N3.92.7WordfenceVulnerability scoring details
Base CVSS 3.1 score
7.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineWordfence
Disclosed
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/cbc3210d-224e-4ed2-ada7-dc17deb17584?source=cveCVE reference, Wordfence
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3267252%40debug-log-manager&new=3267252%40debug-log-manager&sfp_email=&sfph_mail=CVE reference, Wordfence
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.