CVE-2025-10212: CWE-862 Missing Authorization in sitealert SiteAlert (Formerly WP Health)
The SiteAlert (Formerly WP Health) plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on multiple functions in all versions up to, and including, 1.9.8. This makes it possible for unauthenticated attackers to view the site health information, including a list of installed and outdated plugins, PHP and Database version, etc.
AI Analysis
Technical Summary
CVE-2025-10212 is a medium-severity vulnerability affecting the SiteAlert (formerly WP Health) WordPress plugin, versions up to and including 1.9.8. The vulnerability arises from a missing authorization check (CWE-862) on multiple functions within the plugin, allowing unauthenticated attackers to access sensitive site health information. Specifically, attackers can retrieve details such as the list of installed and outdated plugins, PHP version, and database version without any authentication or user interaction. The vulnerability is remotely exploitable over the network (AV:N), requires no privileges (PR:N), and no user interaction (UI:N), making it relatively easy to exploit. However, the impact is limited to confidentiality as the attacker gains read-only access to information that could aid in further attacks but does not allow modification or disruption of the site. The CVSS v3.1 base score is 5.3, reflecting a medium severity level. No known exploits are currently reported in the wild, and no patches have been linked yet. The vulnerability could be leveraged by attackers to perform reconnaissance on WordPress sites using this plugin, potentially identifying outdated components or misconfigurations that could be exploited in subsequent attacks.
Potential Impact
For European organizations, this vulnerability poses a moderate risk primarily related to information disclosure. Attackers gaining access to detailed site health data can identify outdated or vulnerable plugins and software versions, which may facilitate targeted attacks such as privilege escalation, code injection, or ransomware deployment. Organizations in sectors with high regulatory requirements (e.g., finance, healthcare, government) could face compliance risks if sensitive infrastructure details are exposed. Although the vulnerability does not allow direct modification or service disruption, the leaked information could be a stepping stone in multi-stage attacks. Additionally, organizations with public-facing WordPress sites using the SiteAlert plugin may experience reputational damage if attackers exploit this vulnerability to gather intelligence. The risk is heightened for entities that do not regularly update or audit their WordPress plugins and configurations.
Mitigation Recommendations
European organizations should immediately audit their WordPress installations to determine if the SiteAlert (formerly WP Health) plugin is in use, particularly versions up to 1.9.8. If present, organizations should prioritize upgrading to a patched version once available or consider temporarily disabling the plugin to prevent unauthorized data access. In the absence of an official patch, applying custom access controls at the web server or application firewall level to restrict access to the plugin’s endpoints can mitigate exposure. Implementing strict role-based access controls within WordPress to limit plugin visibility and usage is recommended. Regularly monitoring web server logs for suspicious requests targeting SiteAlert endpoints can help detect exploitation attempts. Furthermore, organizations should maintain an up-to-date inventory of WordPress plugins and enforce timely updates to reduce exposure to similar vulnerabilities. Employing a Web Application Firewall (WAF) with rules to block unauthenticated access to sensitive plugin functions can provide an additional layer of defense.
Affected Countries
Germany, United Kingdom, France, Netherlands, Italy, Spain, Poland, Sweden
CVE-2025-10212: CWE-862 Missing Authorization in sitealert SiteAlert (Formerly WP Health)
Description
The SiteAlert (Formerly WP Health) plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on multiple functions in all versions up to, and including, 1.9.8. This makes it possible for unauthenticated attackers to view the site health information, including a list of installed and outdated plugins, PHP and Database version, etc.
AI-Powered Analysis
Technical Analysis
CVE-2025-10212 is a medium-severity vulnerability affecting the SiteAlert (formerly WP Health) WordPress plugin, versions up to and including 1.9.8. The vulnerability arises from a missing authorization check (CWE-862) on multiple functions within the plugin, allowing unauthenticated attackers to access sensitive site health information. Specifically, attackers can retrieve details such as the list of installed and outdated plugins, PHP version, and database version without any authentication or user interaction. The vulnerability is remotely exploitable over the network (AV:N), requires no privileges (PR:N), and no user interaction (UI:N), making it relatively easy to exploit. However, the impact is limited to confidentiality as the attacker gains read-only access to information that could aid in further attacks but does not allow modification or disruption of the site. The CVSS v3.1 base score is 5.3, reflecting a medium severity level. No known exploits are currently reported in the wild, and no patches have been linked yet. The vulnerability could be leveraged by attackers to perform reconnaissance on WordPress sites using this plugin, potentially identifying outdated components or misconfigurations that could be exploited in subsequent attacks.
Potential Impact
For European organizations, this vulnerability poses a moderate risk primarily related to information disclosure. Attackers gaining access to detailed site health data can identify outdated or vulnerable plugins and software versions, which may facilitate targeted attacks such as privilege escalation, code injection, or ransomware deployment. Organizations in sectors with high regulatory requirements (e.g., finance, healthcare, government) could face compliance risks if sensitive infrastructure details are exposed. Although the vulnerability does not allow direct modification or service disruption, the leaked information could be a stepping stone in multi-stage attacks. Additionally, organizations with public-facing WordPress sites using the SiteAlert plugin may experience reputational damage if attackers exploit this vulnerability to gather intelligence. The risk is heightened for entities that do not regularly update or audit their WordPress plugins and configurations.
Mitigation Recommendations
European organizations should immediately audit their WordPress installations to determine if the SiteAlert (formerly WP Health) plugin is in use, particularly versions up to 1.9.8. If present, organizations should prioritize upgrading to a patched version once available or consider temporarily disabling the plugin to prevent unauthorized data access. In the absence of an official patch, applying custom access controls at the web server or application firewall level to restrict access to the plugin’s endpoints can mitigate exposure. Implementing strict role-based access controls within WordPress to limit plugin visibility and usage is recommended. Regularly monitoring web server logs for suspicious requests targeting SiteAlert endpoints can help detect exploitation attempts. Furthermore, organizations should maintain an up-to-date inventory of WordPress plugins and enforce timely updates to reduce exposure to similar vulnerabilities. Employing a Web Application Firewall (WAF) with rules to block unauthenticated access to sensitive plugin functions can provide an additional layer of defense.
Affected Countries
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-09-10T10:41:29.995Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 68dfb274c3835a5fbe033bcb
Added to database: 10/3/2025, 11:24:36 AM
Last enriched: 10/3/2025, 11:34:03 AM
Last updated: 1/7/2026, 4:17:34 AM
Views: 145
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-20893: Origin validation error in Fujitsu Client Computing Limited Fujitsu Security Solution AuthConductor Client Basic V2
HighCVE-2025-14891: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in ivole Customer Reviews for WooCommerce
MediumCVE-2025-14059: CWE-73 External Control of File Name or Path in roxnor EmailKit – Email Customizer for WooCommerce & WP
MediumCVE-2025-12648: CWE-552 Files or Directories Accessible to External Parties in cbutlerjr WP-Members Membership Plugin
MediumCVE-2025-14631: CWE-476 NULL Pointer Dereference in TP-Link Systems Inc. Archer BE400
HighActions
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.