CVE-2026-32375
Missing Authorization in Travel Diaries Plugin Allows Unauthorized Access
Publication date: 2026-03-13
Last updated on: 2026-03-16
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| raratheme | travel_diaries | to 1.2.4 (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-32375 is a Broken Access Control vulnerability in the WordPress Travel Diaries Theme versions up to and including 1.2.4. It occurs due to missing authorization, authentication, or nonce token checks, which allows unauthenticated users to perform actions that should be restricted to higher privileged users.
This means that users without proper permissions can exploit the incorrectly configured access control security levels to carry out unauthorized actions.
How can this vulnerability impact me? :
The vulnerability allows unauthenticated users to perform privileged actions, which could lead to unauthorized changes or access within the Travel Diaries theme.
However, the CVSS score is 5.3, indicating a low severity impact and a low priority for exploitation. It is considered unlikely to be exploited in a harmful manner.
Users are advised to update to version 1.2.5 or later to mitigate this risk.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability is a Broken Access Control issue in the WordPress Travel Diaries Theme up to version 1.2.4, allowing unauthenticated users to perform privileged actions. Detection typically involves checking if the vulnerable theme version is installed.
Since the vulnerability requires no prior authentication to exploit, network detection might be difficult without specific exploit signatures.
A practical approach is to verify the installed theme version on your WordPress site using commands or queries such as:
- Using WP-CLI to check the theme version: wp theme list --status=active
- Manually inspecting the style.css file in the theme directory for the version number.
No specific exploit detection commands or network signatures are provided in the available resources.
What immediate steps should I take to mitigate this vulnerability?
The primary mitigation step is to update the WordPress Travel Diaries Theme to version 1.2.5 or later, which contains the patch for this Broken Access Control vulnerability.
Since the vulnerability allows unauthenticated users to perform privileged actions, applying the update promptly is critical to prevent exploitation.
Additionally, reviewing access control configurations and ensuring proper authorization checks are in place can help reduce risk.