CVE-2025-24776
BaseFortify
Publication date: 2025-06-06
Last updated on: 2026-04-23
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
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?
CVE-2025-24776 is a Broken Access Control vulnerability in the WordPress Responsive Flipbooks plugin (up to version 1.0). It occurs because of missing authorization, authentication, or nonce token checks in certain plugin functions. This allows users with low privileges (Subscriber-level) to perform actions that should be restricted to higher-privileged users. [1]
How can this vulnerability impact me? :
This vulnerability can allow unprivileged users to perform unauthorized actions within the plugin, potentially leading to limited integrity and availability impacts on the affected system. Although the severity is rated low (CVSS 5.4) and exploitation is considered unlikely, attackers could misuse it to alter plugin behavior or disrupt service. There is currently no official patch, but virtual patching is available as a mitigation. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves monitoring for unauthorized actions performed by users with Subscriber-level privileges that should be restricted to higher-privileged users. Since the vulnerability arises from missing authorization checks in certain plugin functions, you can look for unusual access patterns or privilege escalations related to the Responsive Flipbooks plugin. Patchstack recommends professional incident response and server-side malware scanning to detect compromise. Specific commands are not provided in the available resources. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying virtual patching (vPatching) provided by Patchstack to automatically protect against this vulnerability in the absence of an official fix. Additionally, monitor for suspicious activity and consider professional incident response and server-side malware scanning if compromise is suspected. Since no official patch is available, relying on virtual patching and security best practices is recommended. [1]