CVE-2025-58679
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 |
|---|---|---|
| appmysite | appmysite_plugin | 3.14.0 |
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-58679 is a Broken Access Control vulnerability in the WordPress AppMySite Plugin up to version 3.14.0. It occurs due to missing authorization, authentication, or nonce token checks in certain plugin functions, which may allow unauthenticated and unprivileged users to perform actions that should be restricted to higher-privileged users. [1]
How can this vulnerability impact me? :
This vulnerability can allow unauthorized users to perform actions reserved for privileged users, potentially compromising the security of your WordPress site. However, the impact is considered low severity with a CVSS score of 5.3, and it is unlikely to be widely exploited. There is currently no official fix, 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?
Detection involves monitoring for unauthorized access attempts or actions performed by unauthenticated or low-privileged users within the AppMySite plugin functions. Since the vulnerability arises from missing authorization checks, you can look for unusual HTTP requests targeting the plugin endpoints or functions that should require higher privileges. Specific commands are not provided, but you can use web server access logs analysis tools or intrusion detection systems to filter requests to the AppMySite plugin paths and check for suspicious activity. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying virtual patching (vPatching) as recommended by Patchstack, which can auto-mitigate the vulnerability even without an official update. Additionally, monitor for updates from the plugin developer and Patchstack, restrict access to the plugin's administrative functions where possible, and consider implementing additional access control measures at the web server or application firewall level to block unauthorized requests. [1]