CVE-2025-12367
BaseFortify
Publication date: 2025-11-01
Last updated on: 2025-11-04
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordpress | site_seo_plugin | 1.3.1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-285 | The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability in the SiteSEO β SEO Simplified WordPress plugin (up to version 1.3.1) is a Missing Authorization issue. It occurs because the plugin does not properly verify whether a user is authorized to perform certain actions. As a result, authenticated users with Author-level access or higher can enable or disable arbitrary SiteSEO features that they should not have permission to control.
How can this vulnerability impact me? :
This vulnerability allows authenticated users with Author-level access or above to change SiteSEO plugin settings without proper authorization. This could lead to unauthorized enabling or disabling of SEO features, potentially disrupting SEO configurations, affecting website search engine indexing, and possibly degrading site performance or visibility.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves unauthorized changes to SiteSEO plugin settings by authenticated users with Author-level access or higher. Detection can focus on monitoring changes to SiteSEO plugin settings or AJAX actions related to toggling features, importing/exporting/resetting settings, and instant indexing submissions. Since these actions are performed via AJAX calls to ajax.php, you can monitor HTTP POST requests to the ajax.php endpoint of the SiteSEO plugin, especially those that include actions like save_toggle_state, import_settings, reset_settings, and instant_indexing. Commands to detect suspicious activity could include inspecting web server logs for POST requests to ajax.php with these actions, for example using grep: 1. To find AJAX POST requests to ajax.php: `grep 'POST .*ajax.php' /var/log/apache2/access.log` 2. To filter for specific actions in POST data (if logs include POST bodies): `grep -i 'action=save_toggle_state' /var/log/apache2/access.log` or use a web application firewall or intrusion detection system to alert on these actions from users with Author-level access. Additionally, monitoring WordPress user activity logs for unexpected changes to SiteSEO settings or toggles can help detect exploitation attempts. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1. Update the SiteSEO plugin to version 1.3.2 or later, where security improvements and permission checks have been enhanced to prevent unauthorized actions. 2. Restrict user roles and capabilities to ensure only trusted users have Author-level or higher access, as the vulnerability requires at least Author-level access. 3. Monitor and audit SiteSEO plugin settings changes and AJAX requests to detect any unauthorized activity. 4. If updating immediately is not possible, consider temporarily disabling the SiteSEO plugin or restricting access to ajax.php endpoints via web server rules to prevent exploitation. 5. Apply WordPress security best practices such as enforcing strong passwords, limiting login attempts, and using security plugins to monitor suspicious behavior. These steps help prevent attackers from exploiting the missing authorization vulnerability to change SiteSEO plugin settings. [3]