CVE-2025-49509
BaseFortify
Publication date: 2025-06-10
Last updated on: 2026-04-28
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?
This vulnerability is a Broken Access Control issue in the WordPress Audio Editor & Recorder plugin (up to version 2.2.1). It occurs due to missing authorization, authentication, or nonce token checks in certain functions, which allows unauthenticated users to perform actions that should be restricted to higher-privileged users. Essentially, it means that users without proper permissions can exploit the plugin to carry out unauthorized actions. [1]
How can this vulnerability impact me? :
The impact of this vulnerability is that attackers can perform unauthorized actions within the Audio Editor & Recorder plugin without needing to authenticate. This can lead to unauthorized modifications or misuse of the plugin's features, potentially compromising the integrity of your site or data. Although the CVSS score is 5.3 (low severity), it still poses a risk by allowing privilege escalation through broken access control. [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 access attempts to functions reserved for higher-privileged users in the WordPress Audio Editor & Recorder plugin (versions up to 2.2.1). Since the issue is due to missing authorization checks, monitoring web server logs for unusual or unauthorized POST or GET requests targeting the plugin's endpoints can help. Specific commands depend on your environment, but for example, using grep on access logs to find suspicious requests related to the plugin could be useful, e.g., `grep -i 'audio-editor-recorder' /var/log/apache2/access.log` or `grep -i 'audio-editor-recorder' /var/log/nginx/access.log`. Additionally, scanning your WordPress installation for the plugin version can be done with commands like `wp plugin list --format=json | jq '.[] | select(.name=="audio-editor-recorder")'` if WP-CLI is installed. However, no specific detection commands are provided in the resources. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate recommended step to mitigate this vulnerability is to update the WordPress Audio Editor & Recorder plugin to version 2.2.2 or later, where the issue is fixed. If updating immediately is not possible, applying virtual patching (vPatching) offered by Patchstack can provide rapid protection against automated attacks targeting this vulnerability. Additionally, users should monitor for signs of compromise and consider professional incident response if a breach is suspected. [1]