CVE-2026-22393
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 |
|---|---|---|
| mikado-themes | curly | to 3.3 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-639 | The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-22393 is an Insecure Direct Object References (IDOR) vulnerability in the WordPress Curly Theme up to version 3.3. It allows attackers with at least subscriber or developer privileges to bypass authorization and authentication controls, potentially gaining unauthorized access to sensitive files, folders, or database interactions. This is due to incorrectly configured access control security levels. [1]
How can this vulnerability impact me? :
This vulnerability can allow unauthorized users to access sensitive information or perform actions they should not be allowed to, such as viewing or modifying files, folders, or database content. Although the severity is rated low (CVSS 5.4) and exploitation is considered unlikely, it still poses a risk of unauthorized data exposure or manipulation within the affected WordPress site. [1]
What immediate steps should I take to mitigate this vulnerability?
Since no official fix is currently available for this vulnerability, immediate mitigation steps include restricting subscriber or developer privileges to trusted users only, monitoring access to sensitive files and folders, and applying strict access control policies to the WordPress Curly Theme. Additionally, consider disabling or removing the Curly theme if it is not essential to reduce exposure. [1]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not specify how this vulnerability affects compliance with common standards and regulations such as GDPR or HIPAA.