CVE-2025-30990
BaseFortify
Publication date: 2025-06-06
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 |
|---|---|---|
| themehunk | mega_menu | to 1.1.2 (inc) |
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-30990 is a Broken Access Control vulnerability in the WordPress ThemeHunk plugin (up to version 1.1.1). It occurs due to missing authorization, authentication, or nonce token checks in certain functions, which can allow low-privileged users (such as Subscribers) to perform actions that should be restricted to higher-privileged roles. [1]
How can this vulnerability impact me? :
This vulnerability could allow a low-level user to perform unauthorized actions within the ThemeHunk plugin, potentially leading to unauthorized changes or misuse of the website's functionality. However, the risk is considered low severity (CVSS 4.3), and exploitation is unlikely to be widespread. Users should monitor for updates and consider professional incident response if they suspect compromise. [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 low-privilege users (Subscriber role) that should require higher privileges. Since the vulnerability arises from missing authorization checks in certain plugin functions, you can audit WordPress logs for suspicious activity by Subscriber users attempting to access or modify restricted areas. Specific commands are not provided in the resources, but general approaches include reviewing web server logs, WordPress activity logs, and using security plugins to detect abnormal behavior. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying virtual patching (vPatching) provided by Patchstack, which auto-mitigates the vulnerability without requiring an official patch. Additionally, monitor for updates from the plugin developer, restrict Subscriber role capabilities if possible, and consider professional incident response if compromise is suspected. [1]