CVE-2025-12185: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in era404 StaffList
The StaffList plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 3.2.6 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.
AI Analysis
Technical Summary
The StaffList plugin by era404 for WordPress suffers from a stored Cross-Site Scripting (XSS) vulnerability identified as CVE-2025-12185. This vulnerability arises due to improper neutralization of input during web page generation (CWE-79), specifically insufficient input sanitization and output escaping in the plugin's admin settings interface. Authenticated attackers with administrator or higher privileges can inject arbitrary JavaScript code that is stored persistently and executed whenever a user accesses the affected page. This vulnerability is unique to multi-site WordPress installations or those where the unfiltered_html capability is disabled, which restricts users from posting raw HTML content. The CVSS 3.1 base score is 4.4, with vector AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N, indicating network attack vector, high attack complexity, high privileges required, no user interaction, scope changed, and low impact on confidentiality and integrity with no availability impact. Although no public exploits have been reported, the vulnerability could be leveraged for session hijacking, defacement, or privilege escalation within the WordPress environment. The lack of official patches at the time of reporting necessitates immediate attention from administrators to mitigate risk.
Potential Impact
The primary impact of this vulnerability is the potential for attackers with administrator-level access to inject malicious scripts that execute in the context of other users visiting the affected pages. This can lead to theft of session cookies, unauthorized actions performed on behalf of users, or further compromise of the WordPress environment. Since the vulnerability requires high privileges, the risk is somewhat contained but still significant in environments where multiple administrators exist or where compromised admin credentials are possible. The scope change (S:C) means the vulnerability can affect resources beyond the initially compromised component, potentially impacting the entire multi-site network. Organizations relying on the StaffList plugin in multi-site configurations or with unfiltered_html disabled are at risk of targeted attacks that could undermine the integrity and confidentiality of their web applications. The absence of availability impact reduces the risk of denial-of-service conditions but does not diminish the threat to data security and trustworthiness of the site.
Mitigation Recommendations
To mitigate this vulnerability, organizations should first verify if they are running the StaffList plugin in a multi-site WordPress environment or with unfiltered_html disabled. Immediate steps include restricting administrator access to trusted personnel only and auditing admin accounts for suspicious activity. Since no official patch is currently available, administrators should consider temporarily disabling the StaffList plugin or removing it if not essential. Implementing Web Application Firewall (WAF) rules to detect and block suspicious script injections targeting the plugin's admin settings can provide interim protection. Additionally, enabling Content Security Policy (CSP) headers can help mitigate the impact of injected scripts by restricting script execution sources. Regularly monitoring logs for unusual admin activity and educating administrators about the risks of XSS can reduce exploitation likelihood. Once a patch is released, prompt application is critical. Finally, consider isolating multi-site installations or enabling unfiltered_html only where absolutely necessary to reduce attack surface.
Affected Countries
United States, United Kingdom, Germany, Canada, Australia, France, Netherlands, India, Brazil, Japan
CVE-2025-12185: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in era404 StaffList
Description
The StaffList plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 3.2.6 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The StaffList plugin by era404 for WordPress suffers from a stored Cross-Site Scripting (XSS) vulnerability identified as CVE-2025-12185. This vulnerability arises due to improper neutralization of input during web page generation (CWE-79), specifically insufficient input sanitization and output escaping in the plugin's admin settings interface. Authenticated attackers with administrator or higher privileges can inject arbitrary JavaScript code that is stored persistently and executed whenever a user accesses the affected page. This vulnerability is unique to multi-site WordPress installations or those where the unfiltered_html capability is disabled, which restricts users from posting raw HTML content. The CVSS 3.1 base score is 4.4, with vector AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N, indicating network attack vector, high attack complexity, high privileges required, no user interaction, scope changed, and low impact on confidentiality and integrity with no availability impact. Although no public exploits have been reported, the vulnerability could be leveraged for session hijacking, defacement, or privilege escalation within the WordPress environment. The lack of official patches at the time of reporting necessitates immediate attention from administrators to mitigate risk.
Potential Impact
The primary impact of this vulnerability is the potential for attackers with administrator-level access to inject malicious scripts that execute in the context of other users visiting the affected pages. This can lead to theft of session cookies, unauthorized actions performed on behalf of users, or further compromise of the WordPress environment. Since the vulnerability requires high privileges, the risk is somewhat contained but still significant in environments where multiple administrators exist or where compromised admin credentials are possible. The scope change (S:C) means the vulnerability can affect resources beyond the initially compromised component, potentially impacting the entire multi-site network. Organizations relying on the StaffList plugin in multi-site configurations or with unfiltered_html disabled are at risk of targeted attacks that could undermine the integrity and confidentiality of their web applications. The absence of availability impact reduces the risk of denial-of-service conditions but does not diminish the threat to data security and trustworthiness of the site.
Mitigation Recommendations
To mitigate this vulnerability, organizations should first verify if they are running the StaffList plugin in a multi-site WordPress environment or with unfiltered_html disabled. Immediate steps include restricting administrator access to trusted personnel only and auditing admin accounts for suspicious activity. Since no official patch is currently available, administrators should consider temporarily disabling the StaffList plugin or removing it if not essential. Implementing Web Application Firewall (WAF) rules to detect and block suspicious script injections targeting the plugin's admin settings can provide interim protection. Additionally, enabling Content Security Policy (CSP) headers can help mitigate the impact of injected scripts by restricting script execution sources. Regularly monitoring logs for unusual admin activity and educating administrators about the risks of XSS can reduce exploitation likelihood. Once a patch is released, prompt application is critical. Finally, consider isolating multi-site installations or enabling unfiltered_html only where absolutely necessary to reduce attack surface.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-10-24T19:43:22.226Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6927e15abdf69728cfdf7df0
Added to database: 11/27/2025, 5:27:54 AM
Last enriched: 2/27/2026, 8:18:26 PM
Last updated: 3/24/2026, 5:51:05 AM
Views: 141
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.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.