CVE-2026-22447
BaseFortify
Publication date: 2026-01-22
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 |
|---|---|---|
| select-themes | prowess | to 1.8.1 (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-2026-22447 is a Broken Access Control vulnerability in the WordPress Prowess Theme (versions up to 1.8.1). It occurs due to missing authorization, authentication, or nonce token checks in certain functions, which allows unauthenticated users to perform actions that should require higher privileges. [1]
How can this vulnerability impact me? :
This vulnerability can allow unauthorized users to perform privileged actions within the WordPress Prowess Theme, potentially leading to unauthorized changes or access. However, it has a low severity impact with a CVSS score of 4.3 and is considered unlikely to be exploited. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing for missing authorization or broken access control in the WordPress Prowess Theme (version <= 1.8.1). Specifically, you can attempt to access or perform actions that require higher privileges without authentication to see if unauthorized access is possible. Since no official fix or detection scripts are provided, manual testing or custom scripts targeting the theme's functions for missing nonce or authentication checks would be necessary. No specific commands are provided in the available resources. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the affected WordPress Prowess Theme functions by implementing proper authorization checks manually or disabling the theme until a patch is available. Since no official fix or patched version currently exists, monitoring for updates from the theme developer or Patchstack is recommended. Additionally, limiting user privileges and hardening WordPress security settings can reduce the risk of exploitation. [1]