CVE-2025-8152
BaseFortify
Publication date: 2025-08-02
Last updated on: 2025-08-04
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordfence | easy_sticky_sidebar | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform 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?
This vulnerability exists in the WP CTA – Call To Action Plugin, Sticky CTA, Sticky Buttons plugin for WordPress (up to version 1.7.0). It allows unauthenticated attackers to modify data without proper authorization because the plugin's functions 'update_cta_status' and 'change_sticky_sidebar_name' lack necessary capability checks. This means attackers can update the status of sticky CTAs and change the sidebar name displayed in the back-end dashboard without being logged in or having proper permissions.
How can this vulnerability impact me? :
The vulnerability can impact you by allowing unauthorized users to modify the status and names of sticky call-to-action elements on your WordPress site. This unauthorized modification can lead to misleading or malicious content being displayed, potentially affecting user trust and site integrity. However, it does not directly impact confidentiality or availability, as the CVSS score indicates no confidentiality or availability impact but a low integrity impact.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
You can detect this vulnerability by checking if your WordPress installation uses the WP CTA – Call To Action Plugin, Sticky CTA, Sticky Buttons plugin version 1.7.0 or earlier. To identify exploitation attempts, monitor for unauthorized AJAX requests targeting the 'update_cta_status' and 'change_sticky_sidebar_name' functions without proper authentication or nonce verification. On the server, you can search web server logs for POST requests to admin-ajax.php with action parameters 'update_cta_status' or 'change_sticky_sidebar_name' coming from unauthenticated sources. Example command to search Apache logs: `grep 'admin-ajax.php' /var/log/apache2/access.log | grep -E 'action=update_cta_status|action=change_sticky_sidebar_name'`. Additionally, check for suspicious changes in the database tables related to sticky CTA status or sidebar names. Since the vulnerability involves missing capability checks allowing unauthorized data modification, any such unauthorized changes could indicate exploitation. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the WP CTA – Call To Action Plugin, Sticky CTA, Sticky Buttons plugin to a version later than 1.7.0 where the missing capability checks and nonce verifications are implemented. If an update is not immediately available, restrict access to the AJAX endpoints by limiting access to authenticated users only and ensure nonce verification is enforced on all AJAX handlers, especially 'update_cta_status' and 'change_sticky_sidebar_name'. Additionally, monitor and audit changes to sticky CTA statuses and sidebar names in the WordPress backend to detect unauthorized modifications. Applying web application firewall (WAF) rules to block unauthenticated requests to these AJAX actions can also help mitigate exploitation attempts. [1]