sales@hackhalt.com

Home / Threats / CVE-2026-13144

WP Travel - Security Vulnerability (CVE-2026-13144)

CVE-2026-13144

The WP Travel WordPress plugin before 12.0.2 does not properly verify that the requester is authorized to modify the targeted booking on one branch of its bank-deposit handler, allowing an unauthenticated attacker who knows the target customer's email address to reset that customer's booking payment to an unpaid state and wipe its stored deposit-reconciliation data.

CVE-2026-13144

LOW CVSS 3.7 Published 2026-09-09 Updated 2026-09-09
AI Risk Moderate (38/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P4 Planned
Severity Band LOW
CVSS Vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
Affected Components 1
Reference Links 1
AI Risk Engine Moderate (38/100)
Exploitability Low
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2026-09-09 CVE published and first recorded in the threat feed.
  2. 2026-09-09 Record updated with latest vulnerability metadata.
  3. 2026-09-10 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 30 days ago

AI enriched 30 days ago (2026-09-10 18:57 UTC)

Technical Summary

The WP Travel WordPress plugin before 12.0.2 does not properly verify that the requester is authorized to modify the targeted booking on one branch of its bank-deposit handler, allowing an unauthenticated attacker who knows the target customer's email address to reset that customer's booking payment to an unpaid state and wipe its stored deposit-reconciliation data.

Potential Impact

Severity is LOW (CVSS 3.7). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as Low based on low-bar exploit prerequisites.

Primary risk drivers: low-bar exploit prerequisites

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 38/100 (Moderate, Low) with priority P4 Planned. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

WP Travel PLUGIN · wp-travel Affected: < 12.0.2 Fixed in: 12.0.2

References

What to do about this

Patch on your next cycle Worth fixing, but not ahead of other work.

Fix it

Update WP Travel to 12.0.2 or later.

That is the complete fix. Everything below is what protects you in the meantime.

No Hack Halt control meaningfully contains this one — updating is the remedy. We would rather say so than sell you something that will not help.

Start free

Not sure if you are affected?

Scan your site to see whether it runs WP Travel, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?

You are affected if your site runs WP Travel. Versions below 12.0.2 are vulnerable; that release and later are not. No account is needed to exploit this, so a public site is reachable by anyone.

How do I fix it?

Update WP Travel to version 12.0.2 or later. That is the complete fix.