CVE-2025-58824
BaseFortify
Publication date: 2025-09-05
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 |
|---|---|---|
| wordpress | shk_corporate_theme | 2.4.1.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-58824 is a Broken Access Control vulnerability in the WordPress Shk Corporate Theme (up to version 2.4.1.1). It occurs due to missing authorization, authentication, or nonce token checks in certain functions, which may allow unprivileged users (such as those with Subscriber-level privileges) to perform actions that should be restricted to higher-privileged users. This issue falls under the OWASP Top 10 category A1: Broken Access Control. [1]
How can this vulnerability impact me? :
This vulnerability could allow users with low-level privileges to execute actions reserved for higher-privileged users, potentially leading to unauthorized changes or access within the affected WordPress site. Although the severity is rated low (CVSS 4.3) and exploitation is considered unlikely, if exploited, it could compromise the integrity of the site. There is currently no official patch, but virtual patching is available as a mitigation strategy. In case of compromise, professional incident response and server-side malware scanning are recommended. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves monitoring for unauthorized actions performed by users with Subscriber-level privileges that should be restricted to higher-privileged users. Since the issue is due to missing authorization checks in certain functions of the Shk Corporate Theme, detection may require reviewing access logs for suspicious privilege escalations or unauthorized access attempts. No specific commands are provided in the resources. It is recommended to perform server-side malware scanning and professional incident response if compromise is suspected, as plugin-based scanners may be unreliable. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing virtual patching (vPatching) offered by Patchstack, which provides automatic protection against this vulnerability without requiring an official patch and without impacting performance. Users should monitor for updates from the theme developers or Patchstack. In the absence of an official fix, virtual patching is the recommended approach. Additionally, if a compromise is suspected, professional incident response and server-side malware scanning should be conducted. [1]