Skip to main content
Menu
CVEs

CVE

Hotel Booking Lite arbitrary file upload in theme file handler

Hotel Booking Lite WordPress theme version 2.5.1 and earlier is affected. The checked facts list no fixed version or vendor severity rating.

CVE-2026-125851

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

9.9CriticalCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Hotel Booking Lite WordPress theme version 2.5.1 or earlier

Published
Last modified
Reference
Last checked
23/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub

Summary

Unrestricted Upload of File with Dangerous Type vulnerability in themagnifico52 Hotel Booking Lite hotel-booking-lite allows Upload a Web Shell to a Web Server.This issue affects Hotel Booking Lite: from n/a through 2.5.1.

Who should check

Sites running the Hotel Booking Lite WordPress theme version 2.5.1 or earlier, including hotel booking sites built on it.

Read the source excerpt

“WordPress Hotel Booking Lite Theme <= 2.5.1 is vulnerable”

patchstack.com

cve.now Index

23Pcve.now Index 23 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.9/10CVSS 9.9
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 73 if added to CISA KEV
  • Would score about 68 if CISA's SSVC rates exploitation active
  • Would score about 30 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Hotel Booking Lite WordPress theme version 2.5.1 or earlier
  • Workaround: The checked facts include no workaround. Until a fix is published, follow the vendor's guidance, if it gives any.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-125851 (WordPress Hotel Booking Lite theme <= 2.5.1 - Arbitrary File Upload vulnerability), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-125851 (entry last updated 2026-11-13):
Affected:
- themagnifico52 Hotel Booking Lite: through 2.5.1
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Hotel Booking Lite WordPress theme version 2.5.1 or earlier (source: https://patchstack.com/database/wordpress/theme/hotel-booking-lite/vulnerability/wordpress-hotel-booking-lite-theme-2-5-1-arbitrary-file-upload-vulnerability?_s_id=cve)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-125851 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125851 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/theme/hotel-booking-lite/vulnerability/wordpress-hotel-booking-lite-theme-2-5-1-arbitrary-file-upload-vulnerability?_s_id=cve
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-125851
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-125851"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • hotel-booking-lite

    through 2.5.1

Evidence 3

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 1

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-125851

Is CVE-2026-125851 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

Attackers can upload malicious files to the server, and those files can be used to take the server over.Source: patchstack.com

Which versions are affected by CVE-2026-125851?

hotel-booking-lite: through 2.5.1.Source: cve.now feed data

Am I affected, and how do I check?

The affected product is the Hotel Booking Lite WordPress theme by themagnifico52, version 2.5.1 and earlier. The installed theme version is shown under Appearance > Themes in the WordPress admin, or in the Version line of the theme's style.css header.Source: patchstack.com

How do I fix CVE-2026-125851?

The checked facts name no fixed version or vendor patch, so no upgrade target can be given. Check the vendor's theme page for a newer release that is later than 2.5.1.Source: patchstack.com

What if there's no patch?

The checked facts include no workaround. Until a fix is published, follow the vendor's guidance, if it gives any.Source: patchstack.com