CVE-2026-32383
Missing Authorization in Ridhi ≤ 1.1.2 Enables Unauthorized Access
Publication date: 2026-03-13
Last updated on: 2026-04-29
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| raratheme | ridhi | 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
How can this vulnerability impact me? :
The vulnerability allows unauthorized users to perform privileged actions due to missing access control checks.
However, the CVSS severity score is 5.3, indicating a low priority and low severity impact.
It is considered unlikely to be exploited but still poses a risk because of the lack of proper access controls.
Users are advised to update to Ridhi Theme version 1.1.3 or later to mitigate this vulnerability.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
Can you explain this vulnerability to me?
CVE-2026-32383 is a Broken Access Control vulnerability in the WordPress Ridhi Theme versions up to and including 1.1.2.
The issue arises from missing authorization, authentication, or nonce token checks within certain functions, which allows unauthenticated users to perform actions that normally require higher privileges.
This vulnerability falls under the OWASP Top 10 category A1: Broken Access Control.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability arises from missing authorization, authentication, or nonce token checks within certain functions of the Ridhi WordPress theme up to version 1.1.2. Detection would involve verifying if the installed Ridhi theme version is 1.1.2 or earlier.
Since the issue is related to broken access control in the theme, detection commands could include checking the theme version via WordPress CLI or inspecting the theme files for the presence of vulnerable code.
- Use WP-CLI to check the Ridhi theme version: `wp theme list --status=active` and verify if the version is <= 1.1.2.
- Manually inspect the theme files for missing authorization checks in functions if you have access to the source code.
What immediate steps should I take to mitigate this vulnerability?
The primary mitigation step is to update the Ridhi WordPress theme to version 1.1.3 or later, where this vulnerability has been fixed.
Since the vulnerability is due to broken access control, applying the update will restore proper authorization checks and prevent unauthorized actions.
No additional impactful threats have been identified, so updating the theme is the recommended immediate action.