CVE-2026-24607
WordPress vulnerability analysis and mitigation

Overview

CVE-2026-24607 is a Missing Authorization vulnerability in the Travel Monster WordPress theme (by wptravelengine) that allows unauthenticated attackers to exploit incorrectly configured access control security levels. It affects Travel Monster versions up to and including 1.3.3. The vulnerability was published on January 23, 2026, and was assigned by Patchstack. It carries a CVSS v3.1 base score of 5.3 (Medium), with the availability impact being the primary concern per the CNA-assigned vector (Patchstack).

Technical details

The root cause is classified as CWE-862 (Missing Authorization), meaning the theme fails to properly verify whether a requesting user has the necessary permissions before executing certain actions. This allows network-accessible, unauthenticated attackers with no user interaction required to trigger restricted functionality due to incorrectly configured access control levels. No public proof-of-concept code or detailed technical write-up has been identified at this time (Patchstack).

Impact

Successful exploitation primarily results in an availability impact, as reflected in the CNA-assigned CVSS vector (A:L), meaning attackers may be able to disrupt or degrade certain theme functionality without authentication. The confidentiality and integrity of data are not directly impacted per the current assessment. The scope is limited to the affected WordPress installation running the vulnerable Travel Monster theme version.

Exploitability

No evidence of active in-the-wild exploitation has been reported for CVE-2026-24607, and it does not appear in the CISA Known Exploited Vulnerabilities (KEV) catalog. The EPSS score is approximately 0.028%, indicating a very low probability of exploitation in the near term. No public exploit code or weaponized tooling has been identified (Patchstack).

Mitigation and workarounds

Users of the Travel Monster WordPress theme should update to a version beyond 1.3.3 if a patched release is available from the wptravelengine developer. As a general workaround, site administrators can restrict access to sensitive theme functionality via server-level controls or a Web Application Firewall (WAF) while awaiting an official patch. Monitoring WordPress plugin/theme update channels and the Patchstack advisory page is recommended for patch availability (Patchstack).

Additional resources


SourceThis report was generated using AI

Related WordPress vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-77115HIGH7.1
  • brave-popup-builder
NoYesAug 23, 2026
CVE-2026-77116MEDIUM4.3
  • brave-popup-builder
NoYesAug 23, 2026
CVE-2026-14853MEDIUM4.3
  • woocommerce-bookings
NoYesAug 23, 2026
CVE-2026-77003LOW2.7
  • content-mask
NoYesAug 23, 2026
CVE-2026-13598NONEN/A
  • restrictmate
NoYesAug 23, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management