CVE-2025-12855VulnerabilityPublished 7 Nov 2025

CVE-2025-12855: 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 their use of the Responsive Hotel Site version 1.0 and restrict access to the /admin/newsletterdel.php endpoint to trusted administrators only, ideally through network segmentation and IP whitelisting. Implement strict input validation and parameterized queries or prepared statements to prevent SQL injection. Monitor logs for unusual database queries or access patterns indicative of exploitation attempts. Conduct thorough privilege reviews to ensure that only necessary users have high-level access, reducing the attack surface. Plan for an upgrade or migration to a patched or alternative solution once available. Regularly back up databases and test restoration procedures to mitigate potential data loss. Engage in threat intelligence sharing within the hospitality sector to stay informed about emerging exploits.

Description

A security flaw has been discovered in code-projects Responsive Hotel Site 1.0. This issue affects some unknown processing of the file /admin/newsletterdel.php. The manipulation of the argument eid results in sql injection. It is possible to launch the attack remotely. The exploit has been released to the public and may be exploited.

Impact

For European organizations, particularly those in the hospitality and tourism sectors using the Responsive Hotel Site software, this vulnerability poses risks of unauthorized data disclosure, data tampering, and potential service disruption. Attackers with high-level access could exploit the SQL injection to extract sensitive customer information such as personal details and booking data, undermining privacy compliance obligations like GDPR. Integrity of the database could be compromised, affecting business operations and trust. Although the vulnerability requires elevated privileges, insider threats or lateral movement by attackers could facilitate exploitation. The public availability of exploit code increases the likelihood of attacks, potentially leading to reputational damage and regulatory penalties. Smaller hotels or chains relying on this software without robust security controls are particularly vulnerable. The impact is somewhat contained by the need for high privileges, but the risk remains significant for affected entities.

Summary

CVE-2025-12855 identifies a SQL injection vulnerability in the Responsive Hotel Site version 1.0 developed by code-projects. The vulnerability resides in the /admin/newsletterdel.php script, where the 'eid' parameter is improperly sanitized, allowing malicious input to alter SQL queries executed by the backend database. This flaw can be exploited remotely, but the CVSS vector indicates that high privileges (PR:H) are required, meaning an attacker must already have elevated access to the system to leverage the injection. The vulnerability impacts confidentiality, integrity, and availability at a low level, as it could allow unauthorized reading or modification of data and potentially disrupt services. No user interaction is needed, and the attack complexity is low once privileges are obtained. Although no patches have been linked yet, the public release of exploit code increases the risk of exploitation. The vulnerability does not affect system components beyond the specified file and parameter, limiting its scope. The presence of this flaw in a hospitality management system could expose sensitive customer data or administrative functions to attackers, emphasizing the need for prompt remediation.

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