CVE-2025-58680
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 |
|---|---|---|
| gutentor | gutentor | * |
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-58680 is a Broken Access Control vulnerability in the WordPress Gutentor plugin versions up to 3.5.2. It is caused by missing authorization, authentication, or nonce token checks in certain plugin functions, which allows users with contributor-level privileges to perform actions that should be restricted to higher-privileged roles. [1]
How can this vulnerability impact me? :
This vulnerability can allow an attacker with contributor-level access to perform unauthorized actions reserved for higher-privileged users, potentially leading to unauthorized changes or control within the WordPress site. Although the severity is considered low (CVSS 6.5), it can still compromise the integrity of the site if exploited. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability arises from missing authorization checks in the Gutentor WordPress plugin (versions up to 3.5.2) and requires contributor-level access to exploit. Detection involves verifying if the plugin version is vulnerable and monitoring for unauthorized actions by contributor-level users. There are no specific commands provided for detection. It is recommended to perform server-side malware scanning and professional incident response if compromise is suspected. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying Patchstack's virtual patching (vPatching) technology, which provides automatic protection against this vulnerability despite the absence of an official fix. Additionally, restrict contributor-level access where possible, monitor user actions, and conduct professional incident response and server-side malware scanning if compromise is suspected. [1]