CVE-2025-58785
BaseFortify
Publication date: 2025-09-05
Last updated on: 2026-04-28
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordpress | ray_enterprise_translation_plugin | 1.7.1 |
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-58785 is a Broken Access Control vulnerability in the WordPress Ray Enterprise Translation Plugin (up to version 1.7.1). It occurs due to missing authorization, authentication, or nonce token checks in certain functions, which allows users with low-level 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, potentially leading to limited integrity and availability impacts within the affected system. Although the risk is considered low and exploitation unlikely, unauthorized actions could disrupt normal operations or modify data improperly. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection involves monitoring for unauthorized actions performed by users with Subscriber-level privileges that should require higher privileges. Since the vulnerability allows privilege escalation via missing authorization checks in certain plugin functions, you can audit WordPress logs for suspicious activity such as unexpected changes or actions by low-privilege users. Specific commands are not provided in the resources. It is recommended to monitor access logs and WordPress user activity for anomalies. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation includes applying virtual patching (vPatching) provided by Patchstack, which offers automatic protection without performance loss despite no official patch being available. Additionally, monitor for updates from the plugin vendor and consider professional incident response if compromise is suspected. Restricting Subscriber-level user capabilities temporarily may also reduce risk. [1]