Skip to main content

WordPress EUVDEUVD-2025-16984

| CVE-2025-5701 HIGH
Missing Authorization (CWE-862)
2025-06-05 security@wordfence.com
8.8
CVSS 3.1 · NVD
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Impact

This vulnerability presents extreme real-world risk across multiple dimensions: (1) CVSS 9.8 with CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H indicates network-accessible, low-complexity exploitation requiring no privileges or user interaction, with high impact across confidentiality, integrity, and availability; (2) the missing capability check is a fundamental authorization flaw (CWE-862) with trivial exploitability once discovered; (3) the attack chain is fully automatable—an attacker can programmatically discover WordPress sites using the plugin, trigger the vulnerable AJAX handler, and escalate to admin access without user interaction; (4) the privilege escalation vector is particularly severe because it chains directly to account creation and admin role assignment, providing immediate complete system compromise. While EPSS data and KEV candidacy status are not provided in references, the combination of unauthenticated access + network vector + direct privilege escalation + trivial exploitation + high attack automation potential makes this a critical priority regardless of theoretical exploitation metrics. This is not a 'high-CVSS-but-low-risk' scenario; the risk is both high-scoring AND operationally severe.

Exploit ScenarioDerived

A threat actor discovers a WordPress site running the HyperComments plugin (via public version fingerprinting or WordPress.org plugin enumeration). The attacker sends an unauthenticated HTTP POST request to /wp-admin/admin-ajax.php with parameters action=hc_request_handler and crafted option modification data (e.g., option_name=default_role&option_value=administrator and option_name=users_can_register&option_value=1). Due to the missing capability check, the hc_request_handler function processes this request without verifying user authentication or permissions. The attacker then registers a new WordPress user account, which is automatically assigned the administrator role due to the modified default registration role. The attacker logs in with their new admin account and gains full control of the WordPress installation, including access to sensitive data, ability to modify site content, install malicious plugins, and potentially compromise the underlying web server. This entire attack sequence requires zero user interaction, can be completed in seconds, and is easily automatable for scanning and exploiting multiple vulnerable sites at scale.

Act Now Prioritize within 24-48h. Why: HIGH severity + EPSS > 10%.
No patch listed yet 13.8% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 14, 2026

The HyperComments WordPress plugin versions up to 1.2.2 contain a critical missing capability check vulnerability in the hc_request_handler function that allows unauthenticated remote attackers to modify arbitrary WordPress options without authentication. This can be directly exploited to escalate privileges by changing the default registration role to administrator and enabling user registration, granting attackers immediate administrative access to vulnerable sites. With a CVSS score of 9.8 and network-based attack vector requiring no user interaction, this vulnerability poses an extreme risk to any unpatched WordPress installation using the affected plugin.

RemediationAI

Immediate remediation steps: (1) Update the HyperComments plugin to version 1.2.3 or later (if available) or the latest stable release from the official WordPress.org plugin repository, as the vendor should have released a patch adding proper capability checks; (2) If no patch is available or delay is expected, immediately deactivate and remove the HyperComments plugin; (3) Review WordPress site options, particularly the default user role (option_name: 'default_role') and user registration settings (option_name: 'users_can_register') for unauthorized modifications; (4) Audit administrator user accounts for unauthorized additions created post-exploitation; (5) Implement WordPress security hardening: enable two-factor authentication for all admin accounts, restrict AJAX endpoints via security plugins, and implement capability-based access controls. Recommended workaround during patch delay: disable user registration on Settings > General and restrict AJAX handler access via .htaccess or firewall rules blocking requests to wp-admin/admin-ajax.php?action=hc_request_handler. Monitor plugin repository for official patch notification and release notes detailing the authorization fix.

Affected VersionsENISA

HyperComments * ≤1.2.2

Affected Packages

euvd hypercomments no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability exists in the HyperComments plugin for WordPress, a third-party plugin that extends WordPress comment functionality. The root cause is CWE-862 (Missing Authorization / Capability Check), where the hc_request_handler AJAX action handler fails to verify that the requesting user possesses the required WordPress capability (typically 'manage_options') before processing requests to modify site options. WordPress uses a role-based access control system where 'manage_options' capability is typically restricted to administrators. By exploiting the missing capability check on this publicly-accessible AJAX endpoint, unauthenticated attackers can invoke the handler without authentication and directly call update_option() functions to modify critical WordPress configuration. The attack leverages WordPress's standard option update mechanisms against the plugin's insufficient input validation and authorization controls.

Know when WordPress gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 8.8 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

The HyperComments plugin for WordPress is vulnerable to unauthorized modification of data that can lead to privilege escalation due to a missing capability check on the hc_request_handler function in all versions up to, and including, 1.2.2. This makes it possible for unauthenticated attackers to update arbitrary options on the WordPress site. This can be leveraged to update the default role for registration to administrator and enable user registration for attackers to gain administrative user access to a vulnerable site.

Executive ViewAI

Why It Matters

The HyperComments WordPress plugin contains a critical vulnerability allowing unauthenticated attackers to gain administrative access to affected websites without a patch currently available. Any organization using this plugin is at immediate risk of account takeover, data theft, and potential business disruption.

Business Impact: Severe
Compensating Controls

Disable the HyperComments plugin immediately via WordPress admin or file deletion; implement WAF rules to block requests to hc_request_handler function; restrict WordPress administrative access by IP whitelist; enable MFA for all user registration and administrative accounts; disable user registration or manually approve new users; monitor wp_options database table modifications; implement WordPress security plugin to restrict capability modifications.

Threat Intelligence Overview

EPSS Score
13.8%
Top 6% exploitable
Exploit
POC
Public exploit code exists
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 13.8%
Patch available No
Active threat Yes
Deciding rule
HIGH severity + EPSS > 10%
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Out-of-Cycle
Exploitation· derived
Poc
System Exposure· derived
Open
Automatable· derived
No
Human Impact
Very High

Priority Score

78
Low Medium High Critical
KEV: 0
EPSS: +14
CVSS: +44
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

CVE-2016-10033 CRITICAL POC
9.8 Dec 30

The mailSend function in the isMail transport in PHPMailer before 5.2.18 might allow remote attackers to pass extra para

CVE-2016-10045 CRITICAL POC
9.8 Dec 30

The isMail transport in PHPMailer before 5.2.20 might allow remote attackers to pass extra parameters to the mail comman

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

CVE-2024-5084 CRITICAL POC
9.8 May 23

The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil

CVE-2024-44000 CRITICAL POC
9.8 Oct 20

Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote

CVE-2024-8353 CRITICAL POC
9.8 Sep 28

The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all

CVE-2020-36847 CRITICAL POC
9.8 Jul 12

The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner

CVE-2025-11749 CRITICAL POC
9.8 Nov 05

The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint

CVE-2025-27007 CRITICAL POC
9.8 May 01

The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut

CVE-2016-1209 CRITICAL POC
9.8 May 14

The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via

CVE-2024-4443 CRITICAL POC
9.8 May 22

The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based

CVE-2026-63030 CRITICAL POC
9.8 Jul 17

Remote code execution in WordPress 6.9.x (before 6.9.5) and 7.0.x (before 7.0.2) arises from a REST API batch endpoint r

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy