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

CVE-2025-5701 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 13.8%.

Which versions of WordPress are affected by CVE-2025-5701?

The HyperComments WordPress plugin contains a critical vulnerability allowing unauthenticated attackers to gain administrative access to affected websites without a patch currently available.

Is there a public PoC exploit available for CVE-2025-5701?

Yes, a public proof-of-concept exploit is available for CVE-2025-5701. Prioritise patching immediately. EPSS: 13.8%.

How to fix or mitigate CVE-2025-5701?

Within 24 hours: Audit all WordPress installations for HyperComments plugin presence and version; disable the plugin immediately on all affected sites. Within 7 days: Deactivate and remove the plugin entirely; review user access logs for suspicious administrative account creation; reset admin credentials and enforce MFA on all administrator accounts. Within 30 days: Identify alternative commenting solutions; establish vendor patch monitoring process; conduct security assessment of affected systems for compromise indicators.

WordPress CVE-2025-5701

EUVD-2025-16984 HIGH

Missing Authorization (CWE-862)

2025-06-05 security@wordfence.com

WordPress Authentication Bypass Privilege Escalation

8.8

CVSS 3.1 · NVD

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

Lifecycle Timeline

EUVD ID Assigned

Mar 14, 2026 - 17:53 euvd

EUVD-2025-16984

Analysis Generated

Mar 14, 2026 - 17:53 vuln.today

CVE Published

Jun 05, 2025 - 12:15 nvd

HIGH 8.8

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.

AnalysisAI

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.

Technical ContextAI

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.

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.