CVE-2026-125851: Hotel Booking Lite File Upload Flaw
Critical CVSS (9.9) reachable over local.
TL;DR - CVE-2026-125851 is a critical unrestricted file-upload vulnerability in the Hotel Booking Lite WordPress theme through version 2.5.1. - Attackers may upload a web shell and execute code on affected WordPress hosting. - No public PoC or confirmed in-the-wild exploitation is known from the available research. - Site owners should inventory, isolate, patch, disable, or remove affected installations immediately.
What Is the Root Cause?
The root cause is inadequate restriction and validation of uploaded files. A secure upload workflow should:
- Restrict permitted file types with an allowlist.
- Validate file contents rather than trusting filenames or client-supplied MIME types.
- Store uploads outside executable web paths where possible.
- Prevent server-side script execution in directories intended for user content.
- Apply appropriate filesystem permissions and web-server controls.
The available records confirm the dangerous-file upload condition but do not disclose which of these controls failed.
The vulnerability description specifically states that the issue allows an attacker to upload a web shell to a web server. That makes the impact more serious than a benign file-distribution issue: if the uploaded file is interpreted by PHP or another server-side runtime, the attacker may execute commands remotely.
The precise prerequisites remain unknown, including whether an unauthenticated request is sufficient or whether a WordPress account is required. Because the vulnerable code path has not been identified in the supplied material, defenders should not rely on narrowly blocking one presumed URL or parameter. Controls should cover the complete theme functionality, web-server execution behavior, and filesystem activity associated with the affected site.
What Happened?
CVE-2026-125851 affects the Hotel Booking Lite WordPress theme associated with themagnifico52. The vulnerability is classified as an unrestricted upload of a file with a dangerous type. In practical terms, an attacker may be able to submit a server-executable file, such as a PHP web shell, and subsequently invoke it through the web server.
The supplied NVD record does not identify the vulnerable function, endpoint, authentication requirement, nonce handling, or upload-validation logic. Those details cannot be safely inferred from the vulnerability description. Administrators should therefore treat any Internet-facing site running the affected theme as exposed until the theme is updated to a confirmed fixed release or removed.
Analyst’s Take: The missing endpoint and authentication details make narrow signature-based defenses unreliable. Inventory and isolation should come first, followed by remediation or removal, because the stated impact includes web-shell deployment and remote code execution.
| Field | Value |
|---|---|
| CVE ID | CVE-2026-125851 |
| Product | Hotel Booking Lite WordPress theme |
| Developer/vendor | themagnifico52 |
| Affected versions | All versions through 2.5.1; NVD states “from n/a through 2.5.1” |
| CVSS | 9.9, Critical |
| Attack vector | Not returned in the supplied NVD record |
| Authentication required | Not established in the supplied records |
| Patch available | Remediation is indicated, but a definitive fixed version is not established |
| Vulnerability type | Unrestricted Upload of File with Dangerous Type |
| CISA KEV status | Not listed at the time of review |
A successful attack could result in arbitrary code execution under the web-server or WordPress process account. Depending on hosting permissions, the attacker could alter WordPress files, create administrator accounts, steal database credentials, access configuration secrets, establish persistence, or pivot into other systems.
For background on how security teams document and analyze technical evidence, see our forensic imaging glossary.
Who Needs to Act?
Organizations need to act if they operate a WordPress installation using the Hotel Booking Lite theme by themagnifico52. The confirmed affected range is Hotel Booking Lite through version 2.5.1, commonly represented by advisory metadata as <= 2.5.1.
NVD describes the lower bound as “from n/a,” so the available records do not establish a precise earliest affected version.
The available records do not provide a confirmed fixed version number. Patchstack indicates that mitigation or remediation is available, but the retrieved advisory data does not expose a definitive release later than 2.5.1 that can be cited as the fixed version. Do not mark a site remediated solely because it has been updated unless the installed theme version is confirmed to be a vendor-fixed release.
| Scope | Required action |
|---|---|
| Hotel Booking Lite 2.5.1 or earlier | Treat as vulnerable; update to a confirmed fixed release or disable/remove the theme |
| Hotel Booking Lite at an unknown version | Determine the installed version and assume exposure until verified |
| Sites no longer using the theme | Remove it rather than leaving inactive vulnerable code installed |
| Sites unable to update | Disable the theme, block executable uploads, and investigate for compromise |
Managed WordPress providers, agencies, and hosting teams should search all tenants, staging environments, backups, and dormant sites. An inactive but installed vulnerable theme may still represent a risk if another weakness permits file access or if administrators later reactivate it without remediation.
Why Is the CVSS Score Critical?
NVD assigns CVE-2026-125851 a CVSS score of 9.9, placing it in the Critical severity category. The supplied NVD record does not return the complete CVSS vector or individual metric values. Consequently, the precise contributions of attack vector, attack complexity, privileges required, user interaction, scope, confidentiality, integrity, and availability cannot be stated without inventing data.
The score is nevertheless consistent with the potential impact described: an attacker may upload a web shell and obtain remote code execution on a web server. Code execution can affect all three core security properties:
- Confidentiality: Database contents, configuration files, credentials, and secrets may be exposed.
- Integrity: WordPress files, site content, accounts, and settings may be modified.
- Availability: Attackers may delete files, disrupt services, or damage the site.
Administrators should not interpret the missing vector as evidence that authentication is unnecessary. The supplied records do not establish whether the vulnerable upload operation is unauthenticated, requires a low-privilege WordPress account, or depends on another condition.
Until technical details are published, exposure assessments should use the affected product and version range as the primary criteria.
Has CVE-2026-125851 Been Exploited?
CVE-2026-125851 is not currently listed in CISA’s Known Exploited Vulnerabilities catalog. The supplied lookup returned on_kev: false, with no date added, due date, required action, or ransomware campaign designation. CISA has therefore not confirmed exploitation in the wild through the KEV catalog.
No public proof-of-concept repository or exploit code was identified in the supplied research results. The available NVD and advisory information describes the impact but does not provide a reproducible exploit.
The current status is therefore:
- No public PoC identified.
- No confirmed in-the-wild exploitation identified from the supplied sources.
- No current CISA KEV listing.
These findings are not proof that exploitation is absent. WordPress themes are widely deployed, and a file-upload flaw capable of placing a web shell can be attractive to opportunistic attackers. Internet-facing sites should be monitored for exploitation attempts even though the vulnerability is not KEV-listed.
Detection Guidance
Start by building an inventory of WordPress sites and determining whether Hotel Booking Lite is installed, active, or present in a backup or staging environment. WordPress administrators can inspect the installed theme version from the administrative interface.
Where command-line access is available, WP-CLI can provide a repeatable inventory:
wp theme list --fields=name,status,version,update
Run the command from each WordPress installation, or use the hosting platform’s inventory tooling across managed sites. Any result showing hotel-booking-lite at version 2.5.1 or earlier should be escalated.
Because the fixed version is not established, do not assume that an update is sufficient without checking the maintainer’s release information.
Search for Suspicious Files
Look for suspicious files in the WordPress content area and other web-accessible directories. The following searches are triage examples, not proof of compromise:
find wp-content -type f \\
\( -iname '*.php' -o -iname '*.phtml' -o -iname '*.php5' \) \\
-printf '%TY-%Tm-%Td %TH:%TM:%TS %p\\n' \\
| sort -r | head -200
Prioritize recently created or modified files, especially files under upload or media directories. Review them before deletion because they may be useful forensic evidence.
Also inspect WordPress, PHP, and web-server logs for POST requests followed by access to an unusual, newly created path. A generic Apache or Nginx pattern worth investigating is:
POST /... HTTP/1.1 200
GET /wp-content/uploads/.../random-name.php HTTP/1.1 200
The exact endpoint and URL pattern are unknown, so this is a behavioral detection rather than a signature for the vulnerable function. A basic log search can identify candidate upload-and-execute sequences:
grep -E 'POST .* (200|201)|GET .*wp-content/uploads/.*\\.(php|phtml|php5)' \\
/var/log/nginx/access.log /var/log/apache2/access.log 2>/dev/null
Security teams should also check for:
- New administrator accounts.
- Modified theme or plugin files.
- Unexpected scheduled tasks.
- Outbound connections from the PHP process.
- Changes to
wp-config.php. - New files in upload or cache directories.
- Unexpected SSH, FTP, SFTP, or hosting-panel activity.
If compromise is suspected, preserve logs and a forensic copy before making extensive changes.
Remediation and Patching
The confirmed affected range is Hotel Booking Lite through 2.5.1. A definitive fixed version number is not available in the supplied NVD record or retrieved Patchstack metadata.
The correct remediation is to install the first vendor-confirmed release later than 2.5.1 once the maintainer documents it. Do not fabricate or assume a target version.
Until a fixed release can be verified, disable or remove the theme. If the site must remain available, switch to a supported alternative theme and test the replacement in a controlled environment.
A WP-CLI example is:
wp theme deactivate hotel-booking-lite
wp theme delete hotel-booking-lite
Run deletion only after confirming that the theme is not required for rollback, preserving a secured copy if incident response needs it. If the theme is active, deactivate it by switching to a known-good installed theme first:
wp theme activate twentytwentyfour
wp theme delete hotel-booking-lite
The theme name used by WP-CLI can differ from the display name. Confirm the slug with wp theme list before executing removal commands.
Block Script Execution in Upload Directories
As a compensating control, configure the web server to prevent execution of PHP and other server-side scripts in media and upload directories. The exact configuration depends on the server and hosting platform, and it should be tested because incorrectly scoped rules can disrupt legitimate applications.
For Apache, a directory-level rule may resemble:
<Directory "/var/www/html/wp-content/uploads">
Options -ExecCGI
<FilesMatch "\.(php|phtml|php[0-9]*)$">
Require all denied
</FilesMatch>
</Directory>
For Nginx, ensure the PHP handler does not process files beneath the uploads path. A deployment-specific example is:
location ~* ^/wp-content/uploads/.*\.(php|phtml|php[0-9]*)$ {
deny all;
}
Validate configuration syntax and reload through the normal change-management process. These controls reduce the impact of a successful upload but do not replace updating or removing vulnerable code.
Respond to Suspected Compromise
If there is evidence that a web shell was uploaded, treat the site as potentially compromised. Take the following steps:
- Isolate the site where practical.
- Preserve relevant logs and suspicious files.
- Rotate WordPress administrator, hosting, database, FTP/SFTP, API, and deployment credentials.
- Review all privileged accounts.
- Inspect scheduled tasks, plugins, themes, and configuration files.
- Rebuild from a known-good source when integrity cannot be established.
- Notify affected stakeholders according to the incident-response plan.
Deleting one suspicious file is not sufficient because an attacker may have added persistence elsewhere.
References
The NVD record provides the CVE identifier, severity, affected product description, and affected range through version 2.5.1. Its supplied record does not include a CVSS vector, exact vulnerable endpoint, authentication requirement, or fixed version.
The Patchstack advisory identifies the affected range as Hotel Booking Lite <= 2.5.1 and indicates that mitigation or remediation is available. The retrieved advisory content does not establish a definitive fixed version number.
- NVD: CVE-2026-125851
- Patchstack advisory: Hotel Booking Lite arbitrary file upload vulnerability
- CISA Known Exploited Vulnerabilities Catalog
Because CISA does not currently list this CVE and no public PoC was identified in the supplied research, organizations should not downgrade the risk. The ability to upload a web shell makes affected, Internet-facing WordPress sites a priority for inventory, isolation, remediation, and compromise assessment.
This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.