CVE-2025-57994
BaseFortify
Publication date: 2025-09-22
Last updated on: 2026-04-23
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordpress | upcoming_events_lists | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-639 | The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability, identified as CVE-2025-57994, is an Insecure Direct Object References (IDOR) issue in the WordPress Upcoming Events Lists Plugin version 1.4.0 and earlier. It allows unauthorized users with subscriber-level privileges to bypass authorization controls and potentially access sensitive files, folders, or database interactions that they should not have access to. It is classified under OWASP Top 10 A1: Broken Access Control. [1]
How can this vulnerability impact me? :
The impact of this vulnerability is that unauthorized users can bypass access controls and gain access to sensitive information or perform actions that should be restricted. This could lead to information disclosure or limited integrity and availability issues. However, the severity is considered low with a CVSS score of 5.4, and it is unlikely to be widely exploited. 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?
There are no specific detection commands or network indicators provided for this vulnerability. Monitoring for unauthorized access attempts by subscriber-level users to restricted resources may help, but no explicit detection commands are available. [1]
What immediate steps should I take to mitigate this vulnerability?
Since no official patch is available, it is recommended to apply virtual patching (vPatching) offered by Patchstack to automatically protect against this vulnerability. Additionally, monitor for updates from the plugin developer and consider restricting subscriber-level access where possible. [1]