LiveActive security incident?Get immediate response
CVE Record

CVE-2023-25051: WordPress Comment Reply Notification Plugin <= 1.4 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Denishua Comment Reply Notification plugin <= 1.4 versions.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a CSRF issue in the WordPress Comment Reply Notification plugin. If a vulnerable site uses version 1.4 or earlier, an attacker may be able to cause a logged-in user’s browser to make an unintended plugin-related change. The published impact is limited to integrity, not data theft or service outage.

Executive priority

Treat as a moderate WordPress hygiene issue. It is not described as actively exploited, but vulnerable public websites should be checked because compromise could alter site behavior or settings through user interaction.

Technical view

CVE-2023-25051 is CWE-352 affecting Denishua Comment Reply Notification for WordPress, described for versions <= 1.4. CVSS 3.1 is 4.3: network reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, low integrity impact, no confidentiality or availability impact.

Likely exposure

Exposure is likely limited to WordPress sites with the Denishua Comment Reply Notification plugin installed, especially version 1.4 or earlier. The provided bundle does not include CPEs or detailed affected-version metadata.

Exploitation context

The CVE is not listed as CISA KEV, and the supplied sources do not state active exploitation. The CVSS vector requires user interaction, consistent with CSRF-style risk where a victim’s existing browser session is abused.

Researcher notes

Evidence is limited to CVE metadata and a Patchstack VDB reference. The bundle identifies CSRF and <= 1.4, but does not provide exploit details, fixed-version details, CPEs, or vendor mitigation language.

Mitigation direction

  • Inventory WordPress sites for the Comment Reply Notification plugin.
  • Check vendor and Patchstack guidance for a fixed version or official workaround.
  • Disable or remove the plugin where it is not business-critical.
  • Restrict administrative access and reduce unnecessary logged-in browsing exposure.
  • Prioritize remediation on externally managed or high-value WordPress sites.

Validation and detection

  • Confirm whether the plugin package comment-reply-notification is installed.
  • Record installed plugin version and compare against <= 1.4.
  • Review WordPress admin activity for unexpected plugin setting changes.
  • Verify whether compensating controls are documented for affected sites.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

CWE-352: 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 lookup
cve · low confidence lookup

CVE-2023-25051 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2023-25051Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
DenishuaComment Reply Notificationcomment-reply-notification, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.