CVE-2025-12354: CWE-862 Missing Authorization in dojodigital Live CSS Preview
The Live CSS Preview plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'wp_ajax_frontend_save' AJAX endpoint in all versions up to, and including, 2.0.0. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update the plugin's css setting.
AI Analysis
Technical Summary
The vulnerability identified as CVE-2025-12354 affects the Live CSS Preview plugin for WordPress, developed by dojodigital. The issue stems from a missing capability check on the AJAX endpoint 'wp_ajax_frontend_save', which is responsible for saving CSS settings dynamically. In WordPress, AJAX endpoints typically require proper authorization to ensure only privileged users can modify sensitive data. However, in this case, the plugin fails to verify whether the requesting user has sufficient permissions before allowing CSS modifications. Consequently, any authenticated user with at least Subscriber-level access—which is a low-privilege role—can exploit this flaw to alter the plugin's CSS settings. This can lead to unauthorized changes in the website's appearance or potentially introduce malicious CSS that could affect user experience or facilitate further attacks such as UI redressing. The vulnerability does not expose confidential data nor does it affect system availability, but it compromises data integrity by allowing unauthorized modifications. The CVSS v3.1 score is 4.3 (medium severity), reflecting the ease of exploitation (network accessible, low privileges required, no user interaction) but limited impact scope (integrity only). No patches or known exploits are currently documented, but the vulnerability affects all versions up to and including 2.0.0 of the plugin. The flaw is categorized under CWE-862 (Missing Authorization).
Potential Impact
The primary impact of this vulnerability is unauthorized modification of CSS settings within the affected WordPress plugin. For organizations, this can lead to defacement or manipulation of website appearance, potentially damaging brand reputation and user trust. Malicious CSS could also be used to create deceptive interfaces, tricking users into performing unintended actions or exposing them to phishing attempts. While the vulnerability does not directly compromise sensitive data or availability, the integrity breach can serve as a foothold for further attacks or social engineering. Since the exploit requires only Subscriber-level access, any compromised or malicious low-privilege user account can be leveraged. This increases risk in environments with many registered users or where account creation is open. The absence of known exploits suggests limited active threat currently, but the vulnerability’s presence in a widely used CMS plugin means it could be targeted in the future. Organizations relying on this plugin for live CSS editing should consider the risk of unauthorized visual modifications and potential downstream impacts on user trust and security posture.
Mitigation Recommendations
Organizations should first verify if they are using the Live CSS Preview plugin version 2.0.0 or earlier. If so, they should monitor the vendor’s channels for an official patch and apply it immediately once available. In the absence of a patch, administrators can mitigate risk by restricting user roles that have access to the plugin’s features, ensuring that only trusted users have Subscriber-level or higher accounts. Implementing web application firewalls (WAF) with custom rules to block unauthorized AJAX calls to 'wp_ajax_frontend_save' can reduce exposure. Additionally, auditing user accounts for suspicious or unnecessary Subscriber-level users and enforcing strong authentication policies will limit potential exploitation. Reviewing and hardening WordPress security configurations, including limiting plugin usage and monitoring changes to CSS files, can help detect and prevent unauthorized modifications. Regular backups of website files and configurations will aid in recovery if unauthorized changes occur.
Affected Countries
United States, United Kingdom, Germany, Canada, Australia, India, Brazil, France, Japan, Netherlands
CVE-2025-12354: CWE-862 Missing Authorization in dojodigital Live CSS Preview
Description
The Live CSS Preview plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'wp_ajax_frontend_save' AJAX endpoint in all versions up to, and including, 2.0.0. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update the plugin's css setting.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability identified as CVE-2025-12354 affects the Live CSS Preview plugin for WordPress, developed by dojodigital. The issue stems from a missing capability check on the AJAX endpoint 'wp_ajax_frontend_save', which is responsible for saving CSS settings dynamically. In WordPress, AJAX endpoints typically require proper authorization to ensure only privileged users can modify sensitive data. However, in this case, the plugin fails to verify whether the requesting user has sufficient permissions before allowing CSS modifications. Consequently, any authenticated user with at least Subscriber-level access—which is a low-privilege role—can exploit this flaw to alter the plugin's CSS settings. This can lead to unauthorized changes in the website's appearance or potentially introduce malicious CSS that could affect user experience or facilitate further attacks such as UI redressing. The vulnerability does not expose confidential data nor does it affect system availability, but it compromises data integrity by allowing unauthorized modifications. The CVSS v3.1 score is 4.3 (medium severity), reflecting the ease of exploitation (network accessible, low privileges required, no user interaction) but limited impact scope (integrity only). No patches or known exploits are currently documented, but the vulnerability affects all versions up to and including 2.0.0 of the plugin. The flaw is categorized under CWE-862 (Missing Authorization).
Potential Impact
The primary impact of this vulnerability is unauthorized modification of CSS settings within the affected WordPress plugin. For organizations, this can lead to defacement or manipulation of website appearance, potentially damaging brand reputation and user trust. Malicious CSS could also be used to create deceptive interfaces, tricking users into performing unintended actions or exposing them to phishing attempts. While the vulnerability does not directly compromise sensitive data or availability, the integrity breach can serve as a foothold for further attacks or social engineering. Since the exploit requires only Subscriber-level access, any compromised or malicious low-privilege user account can be leveraged. This increases risk in environments with many registered users or where account creation is open. The absence of known exploits suggests limited active threat currently, but the vulnerability’s presence in a widely used CMS plugin means it could be targeted in the future. Organizations relying on this plugin for live CSS editing should consider the risk of unauthorized visual modifications and potential downstream impacts on user trust and security posture.
Mitigation Recommendations
Organizations should first verify if they are using the Live CSS Preview plugin version 2.0.0 or earlier. If so, they should monitor the vendor’s channels for an official patch and apply it immediately once available. In the absence of a patch, administrators can mitigate risk by restricting user roles that have access to the plugin’s features, ensuring that only trusted users have Subscriber-level or higher accounts. Implementing web application firewalls (WAF) with custom rules to block unauthorized AJAX calls to 'wp_ajax_frontend_save' can reduce exposure. Additionally, auditing user accounts for suspicious or unnecessary Subscriber-level users and enforcing strong authentication policies will limit potential exploitation. Reviewing and hardening WordPress security configurations, including limiting plugin usage and monitoring changes to CSS files, can help detect and prevent unauthorized modifications. Regular backups of website files and configurations will aid in recovery if unauthorized changes occur.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-10-27T15:17:32.188Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69327c01f88dbe026c7c158f
Added to database: 12/5/2025, 6:30:25 AM
Last enriched: 2/27/2026, 8:22:42 PM
Last updated: 3/25/2026, 5:02:34 PM
Views: 142
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.