CVE-2025-4047: CWE-862 Missing Authorization in wpmudev Broken Link Checker
The Broken Link Checker plugin for WordPress is vulnerable to unauthorized data access due to a missing capability check on the ajax_full_status and ajax_dashboard_status functions in all versions up to, and including, 2.4.4. This makes it possible for authenticated attackers, with Subscriber-level access and above, to view the plugin's status.
AI Analysis
Technical Summary
CVE-2025-4047 is a security vulnerability identified in the Broken Link Checker plugin for WordPress, developed by wpmudev. The vulnerability stems from a missing authorization check (CWE-862) in two AJAX functions: ajax_full_status and ajax_dashboard_status. These functions fail to verify whether the requesting user has the appropriate capabilities before disclosing the plugin's status information. As a result, any authenticated user with Subscriber-level access or higher can exploit this flaw to access potentially sensitive plugin status data that should otherwise be restricted. The vulnerability affects all versions of the plugin up to and including version 2.4.4. The CVSS v3.1 base score is 4.3, indicating a medium severity level. The attack vector is network-based (AV:N), requires low attack complexity (AC:L), and privileges at the level of an authenticated user (PR:L). No user interaction is required (UI:N), and the impact is limited to confidentiality (C:L) without affecting integrity or availability. No known exploits have been reported in the wild as of the publication date. The vulnerability does not allow privilege escalation or code execution but could enable unauthorized disclosure of plugin operational data, which might aid attackers in reconnaissance or further targeted attacks.
Potential Impact
For European organizations using WordPress sites with the Broken Link Checker plugin, this vulnerability poses a moderate risk. Although the direct impact is limited to unauthorized disclosure of plugin status information, such data could reveal insights into site structure, plugin configurations, or operational states that attackers might leverage for more sophisticated attacks. Organizations with multiple user roles, including subscribers or contributors, are particularly at risk since these lower-privileged users can access information beyond their intended scope. This could be exploited in insider threat scenarios or by compromised accounts. The impact is primarily on confidentiality, with no direct effect on data integrity or site availability. However, the information leakage could facilitate social engineering or targeted phishing campaigns against European entities. Given the widespread use of WordPress across Europe for business, governmental, and non-profit websites, the vulnerability could have broad implications if left unmitigated.
Mitigation Recommendations
European organizations should immediately verify if their WordPress installations use the Broken Link Checker plugin, particularly versions up to 2.4.4. Since no official patch links are provided yet, administrators should consider the following steps: 1) Restrict plugin usage to trusted users only, minimizing the number of Subscriber-level or higher accounts; 2) Implement strict role-based access controls and audit user permissions to ensure minimal privilege; 3) Employ Web Application Firewalls (WAFs) to monitor and block suspicious AJAX requests targeting the vulnerable functions; 4) Temporarily disable or remove the Broken Link Checker plugin if it is not essential; 5) Monitor logs for unusual access patterns to ajax_full_status and ajax_dashboard_status endpoints; 6) Stay alert for vendor updates or patches and apply them promptly once available; 7) Educate users about the risks of account compromise and enforce strong authentication mechanisms to reduce the risk of unauthorized access. These targeted mitigations go beyond generic advice by focusing on access control, monitoring, and temporary risk reduction until a patch is released.
Affected Countries
Germany, France, United Kingdom, Italy, Spain, Netherlands, Poland, Sweden
CVE-2025-4047: CWE-862 Missing Authorization in wpmudev Broken Link Checker
Description
The Broken Link Checker plugin for WordPress is vulnerable to unauthorized data access due to a missing capability check on the ajax_full_status and ajax_dashboard_status functions in all versions up to, and including, 2.4.4. This makes it possible for authenticated attackers, with Subscriber-level access and above, to view the plugin's status.
AI-Powered Analysis
Technical Analysis
CVE-2025-4047 is a security vulnerability identified in the Broken Link Checker plugin for WordPress, developed by wpmudev. The vulnerability stems from a missing authorization check (CWE-862) in two AJAX functions: ajax_full_status and ajax_dashboard_status. These functions fail to verify whether the requesting user has the appropriate capabilities before disclosing the plugin's status information. As a result, any authenticated user with Subscriber-level access or higher can exploit this flaw to access potentially sensitive plugin status data that should otherwise be restricted. The vulnerability affects all versions of the plugin up to and including version 2.4.4. The CVSS v3.1 base score is 4.3, indicating a medium severity level. The attack vector is network-based (AV:N), requires low attack complexity (AC:L), and privileges at the level of an authenticated user (PR:L). No user interaction is required (UI:N), and the impact is limited to confidentiality (C:L) without affecting integrity or availability. No known exploits have been reported in the wild as of the publication date. The vulnerability does not allow privilege escalation or code execution but could enable unauthorized disclosure of plugin operational data, which might aid attackers in reconnaissance or further targeted attacks.
Potential Impact
For European organizations using WordPress sites with the Broken Link Checker plugin, this vulnerability poses a moderate risk. Although the direct impact is limited to unauthorized disclosure of plugin status information, such data could reveal insights into site structure, plugin configurations, or operational states that attackers might leverage for more sophisticated attacks. Organizations with multiple user roles, including subscribers or contributors, are particularly at risk since these lower-privileged users can access information beyond their intended scope. This could be exploited in insider threat scenarios or by compromised accounts. The impact is primarily on confidentiality, with no direct effect on data integrity or site availability. However, the information leakage could facilitate social engineering or targeted phishing campaigns against European entities. Given the widespread use of WordPress across Europe for business, governmental, and non-profit websites, the vulnerability could have broad implications if left unmitigated.
Mitigation Recommendations
European organizations should immediately verify if their WordPress installations use the Broken Link Checker plugin, particularly versions up to 2.4.4. Since no official patch links are provided yet, administrators should consider the following steps: 1) Restrict plugin usage to trusted users only, minimizing the number of Subscriber-level or higher accounts; 2) Implement strict role-based access controls and audit user permissions to ensure minimal privilege; 3) Employ Web Application Firewalls (WAFs) to monitor and block suspicious AJAX requests targeting the vulnerable functions; 4) Temporarily disable or remove the Broken Link Checker plugin if it is not essential; 5) Monitor logs for unusual access patterns to ajax_full_status and ajax_dashboard_status endpoints; 6) Stay alert for vendor updates or patches and apply them promptly once available; 7) Educate users about the risks of account compromise and enforce strong authentication mechanisms to reduce the risk of unauthorized access. These targeted mitigations go beyond generic advice by focusing on access control, monitoring, and temporary risk reduction until a patch is released.
Affected Countries
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-04-28T19:30:54.272Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 683ee1eb182aa0cae2739657
Added to database: 6/3/2025, 11:52:11 AM
Last enriched: 7/11/2025, 7:01:55 AM
Last updated: 1/7/2026, 5:24:25 AM
Views: 52
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-0650: CWE-306 Missing Authentication for Critical Function in OpenFlagr Flagr
CriticalCVE-2025-15474: CWE-770 Allocation of Resources Without Limits or Throttling in AuntyFey AuntyFey Smart Combination Lock
MediumCVE-2025-14468: CWE-352 Cross-Site Request Forgery (CSRF) in mohammed_kaludi AMP for WP – Accelerated Mobile Pages
MediumCVE-2025-9611: CWE-749 Exposed Dangerous Method or Function in Microsoft Playwright
HighCVE-2026-22162
UnknownActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.