What is the CVSS score of CVE-2025-31061?

CVE-2025-31061 has a CVSS 3.1 base score of 7.1 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L. EPSS exploitation probability: 0.0%.

Which versions of Wordpress Plugin are affected by CVE-2025-31061?

A reflected Cross-Site Scripting (XSS) vulnerability in the redqteam Wishlist application (versions through 2.1.0) allows attackers to inject malicious code that executes in users' browsers.

How to fix or mitigate CVE-2025-31061?

Within 24 hours: Inventory all systems running redqteam Wishlist and assess user exposure; implement Web Application Firewall (WAF) rules to block reflected XSS payloads targeting the Wishlist component. Within 7 days: Disable the Wishlist feature if non-critical, or restrict access to trusted internal networks only; conduct user awareness training on phishing risks. Within 30 days: Evaluate alternative wishlist solutions or monitor for vendor patch release; perform security code review of custom integrations with the Wishlist module.

Wordpress Plugin CVE-2025-31061

EUVD-2025-17497 HIGH

Cross-site Scripting (XSS) (CWE-79)

2025-06-09 audit@patchstack.com

WordPress XSS Wordpress Plugin

7.1

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.1 HIGH

AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

Low

Lifecycle Timeline

Re-analysis Queued

Apr 23, 2026 - 15:42 vuln.today

cvss_changed

EUVD ID Assigned

Mar 14, 2026 - 19:21 euvd

EUVD-2025-17497

Analysis Generated

Mar 14, 2026 - 19:21 vuln.today

CVE Published

Jun 09, 2025 - 16:15 nvd

HIGH 7.1

DescriptionCVE.org

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in redqteam Wishlist allows Reflected XSS. This issue affects Wishlist: from n/a through 2.1.0.

AnalysisAI

Reflected Cross-Site Scripting (XSS) vulnerability in redqteam's Wishlist plugin affecting versions up to 2.1.0. An unauthenticated attacker can craft malicious URLs containing unfiltered input that executes arbitrary JavaScript in a victim's browser when clicked, potentially leading to session hijacking, credential theft, or malware distribution. The vulnerability has a CVSS score of 7.1 (High) with network-based attack vector requiring user interaction; current KEV/EPSS status and active exploitation details are not provided in available intelligence.

Technical ContextAI

This vulnerability stems from CWE-79 (Improper Neutralization of Input During Web Page Generation), a classic web application flaw where user-supplied input is reflected in HTTP responses without proper encoding or sanitization. The Wishlist plugin, developed by redqteam, fails to sanitize query parameters or form inputs before rendering them in the HTML response. Reflected XSS differs from stored XSS in that the payload is not persisted in a database—instead, it lives in the URL itself, making it suitable for social engineering attacks via email or malicious links. The affected product range (n/a through 2.1.0) suggests no previous patches existed or version tracking began after initial vulnerable code. CPE identification would typically be: cpe:2.3:a:redqteam:wishlist:*:*:*:*:*:*:*:* (version range 0-2.1.0), though exact CPE notation is not provided in the vulnerability source.

RemediationAI

Immediate: Update redqteam Wishlist plugin to version 2.1.1 or later once released (verify vendor release notes for patch confirmation). 2. Workarounds (if patch unavailable): Implement Web Application Firewall (WAF) rules to block requests containing common XSS payloads (e.g., <script>, javascript:, onerror=); enforce Content Security Policy (CSP) headers (Content-Security-Policy: default-src 'self'; script-src 'self') to mitigate reflected XSS impact. 3. Mitigation: Disable the Wishlist plugin on production systems until patched; use an alternative plugin with active security maintenance. 4. Developer patch (if vendor unresponsive): Sanitize all user inputs using appropriate encoding (HTML entity encoding for reflected output, htmlspecialchars() in PHP, or framework equivalents). 5. Monitoring: Audit logs for suspicious query parameters; monitor for signs of session hijacking or unauthorized account access.