CVE-2025-49241
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-49241 is a Broken Access Control vulnerability in the WordPress oik plugin up to version 4.15.1. It occurs due to missing authorization, authentication, or nonce token checks in certain functions, which allows users with only Subscriber-level privileges to perform actions that should be restricted to higher-privileged roles. [1]
How can this vulnerability impact me? :
This vulnerability can allow unprivileged users to perform unauthorized actions within the WordPress site using the oik plugin, potentially leading to unauthorized access or changes. Although the risk is considered low with a CVSS score of 5.3, automated attacks targeting such vulnerabilities are common. If exploited, it may require professional incident response or server-side malware scanning to remediate. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves checking for unauthorized actions performed by Subscriber-level users in the WordPress oik plugin up to version 4.15.1. Since the issue is due to missing authorization checks, monitoring logs for unexpected privilege escalations or actions reserved for higher roles can help. There are no specific commands provided for detection, but professional incident response or server-side malware scanning is recommended over plugin-based scanners to identify compromise. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the oik plugin to version 4.15.2 or later, where the vulnerability is fixed. Alternatively, Patchstack offers virtual patching (vPatching) to auto-mitigate this vulnerability before official patches are applied. Additionally, monitoring and restricting Subscriber-level privileges and applying professional incident response if compromise is suspected are advised. [1]