WordPress WP Travel plugin <= 12.0.3 - Broken Authentication vulnerability

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps WP Travel/WP Travel (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for WP Travel/WP Travel.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Sep 10, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 10, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 10, 2026

Sources and claim methodology

• Source referencepatchstack.com

Related CVEs

• WordPress MailMunch – Grow your Email List plugin <= 3.2.5 - Broken Authentication vulnerabilityAlso CWE-288
• WordPress IMPress for IDX Broker plugin <= 3.3.0 - Broken Authentication vulnerabilityAlso CWE-288
• Stored XSS in Ankaref's LIBRID/LIBREFSame generic ecosystem
• Stored XSS Yönetim panel in Ankaref's LIBRID/LIBREFSame generic ecosystem
• Type confusion in Zephyr HL78xx GNSS NMEA driver causes wild-pointer write from GNSS inputSame generic ecosystem
• Suricata lua/tls: null dereference in TlsGetCertInfoSame generic ecosystem