CVE-2025-12856VulnerabilityPublished 7 Nov 2025

CVE-2025-12856: code-projects Responsive Hotel Site · SQL Injection

Affects code-projects Responsive Hotel SiteSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 7 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
code-projects Responsive Hotel Site	Affected =1.0	Fixed in–

AI-suggested

Organizations should immediately audit access controls to ensure only trusted administrators have access to the /admin/reservation.php interface. Implement strict input validation and parameterized queries to prevent SQL injection, even if patches are not yet available. Monitor logs for unusual database query patterns or failed login attempts that could indicate exploitation attempts. Employ multi-factor authentication (MFA) for administrative accounts to reduce the risk of credential compromise. Network segmentation should isolate administrative interfaces from public-facing systems. Regularly back up databases to enable recovery in case of data tampering. Stay alert for official patches or updates from code-projects and apply them promptly once released. Conduct security awareness training for staff to recognize phishing or social engineering attempts that could lead to credential theft. Consider deploying web application firewalls (WAFs) with custom rules to detect and block SQL injection payloads targeting the vulnerable parameter.

Description

A weakness has been identified in code-projects Responsive Hotel Site 1.0. Impacted is an unknown function of the file /admin/reservation.php. This manipulation of the argument email causes sql injection. The attack can be initiated remotely. The exploit has been made available to the public and could be exploited.

Impact

For European organizations, particularly those in the hospitality and tourism sectors using the Responsive Hotel Site 1.0, this vulnerability could lead to unauthorized access to reservation data, manipulation of booking records, and potential leakage of customer information. This could result in reputational damage, regulatory penalties under GDPR for data breaches, and operational disruptions. Since the vulnerability requires authenticated access, insider threats or compromised credentials pose the greatest risk. The impact on confidentiality is moderate due to potential data exposure, while integrity could be compromised by unauthorized data modifications. Availability impact is limited but possible if attackers manipulate database queries to disrupt service. Given the importance of tourism to many European economies, exploitation could have broader economic consequences, especially in countries with high volumes of hotel bookings and online reservation systems.

Summary

CVE-2025-12856 identifies a SQL injection vulnerability in the Responsive Hotel Site version 1.0 developed by code-projects. The flaw exists in the /admin/reservation.php file, where the email parameter is improperly sanitized, allowing an attacker to inject malicious SQL code. This vulnerability can be exploited remotely but requires the attacker to have high-level privileges (authentication) on the system. The injection could lead to unauthorized access or modification of the backend database, potentially exposing sensitive reservation data or altering booking information. The CVSS 4.0 score is 5.1 (medium), reflecting the need for authentication and limited impact on confidentiality, integrity, and availability. No user interaction is required, and the attack complexity is low. Although no active exploitation has been reported, the availability of public exploit code increases the risk of future attacks. The vulnerability does not affect the system's scope beyond the authenticated administrative interface, limiting its reach but still posing a significant risk to affected organizations. No official patches have been released yet, emphasizing the need for immediate mitigations.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Nov 2025, 14:40 UTC

Technical details

References

Community reviews

Related threats