Security Resilience

CVE-2025-31623

CSRF

Published
31 March 2025
Modified
23 April 2026
CVSS Score v3.1 7.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
EPSS Score 0.0014 3th percentile
Risk Priority 51 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-31623 is a high-severity CSRF (CWE-352) vulnerability. Its CVSS base score is 7.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Internal Defacement (T1491.001); ranked at the 3th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SC-23 (Session Authenticity) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-31623 is a Cross-Site Request Forgery (CSRF) vulnerability, classified under CWE-352, in the richtexteditor Rich Text Editor WordPress plugin that enables Stored XSS. Published on 2025-03-31, it affects all versions of the plugin from n/a through 1.0.1, carrying a CVSS v3.1 base score of 7.1 (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L).

Unauthenticated attackers can exploit this vulnerability remotely with low complexity, requiring only user interaction such as tricking a victim into visiting a malicious page or clicking a forged link. Exploitation via CSRF allows injection of Stored XSS payloads, achieving low impacts on confidentiality, integrity, and availability while changing scope to impact other users or components viewing the tainted content.

The Patchstack advisory at https://patchstack.com/database/Wordpress/Plugin/richtexteditor/vulnerability/wordpress-rich-text-editor-plugin-1-0-1-csrf-to-stored-xss-vulnerability?_s_id=cve details the vulnerability in the WordPress Rich Text Editor plugin version 1.0.1 and provides associated mitigation guidance.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Cross-Site Request Forgery (CSRF) vulnerability in richtexteditor Rich Text Editor richtexteditor allows Stored XSS.This issue affects Rich Text Editor: from n/a through <= 1.0.1.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1491.001 Internal Defacement Impact
An adversary may deface systems internal to an organization in an attempt to intimidate or mislead users, thus discrediting the integrity of the systems.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-8026Shared CWE-352
CVE-2024-3151Shared CWE-352
CVE-2024-24820Shared CWE-352
CVE-2025-23712Shared CWE-352
CVE-2023-37891Shared CWE-352
CVE-2025-48255Shared CWE-352
CVE-2025-29722Shared CWE-352
CVE-2025-8891Shared CWE-352
CVE-2025-9899Shared CWE-352
CVE-2025-30980Shared CWE-352

Affected Assets

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V3.3.2
  • V3.5.1
  • V10.2.1

Mitigating Controls (NIST 800-53 r5) AI

Access enforcement requires verifying that state-changing requests originate from the authenticated user rather than a forged cross-site source.

Protecting session authenticity prevents attackers from replaying or forging authenticated requests via the victim's browser.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly require anti-CSRF controls such as tokens or SameSite attributes.

References