CVE-2025-12856
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA SQL injection vulnerability exists in the /admin/reservation.php file of Responsive Hotel Site 1.0. The 'email' parameter is not properly sanitized, allowing an attacker to inject malicious SQL queries. This can lead to unauthorized database access, data exfiltration, or potentially remote code execution depending on database configuration.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Responsive Hotel Site is installedLocate the web application files - typically in the web server document root (e.g., /var/www/html, /www, or C:\inetpub\wwwroot). Look for files matching this CMS structure.Affected if The Fabian Responsive Hotel Site is present on the server.
-
Confirm the installed versionCheck for a version file, about page, or footer that displays the software version. Compare against version 1.0.Affected if The installed version is exactly 1.0.
-
Verify the vulnerable file existsCheck for the presence of /admin/reservation.php in the web root. This is the file containing the SQL injection flaw.Affected if The file /admin/reservation.php exists in the application directory.
-
Determine if admin interface is exposedAttempt to access the /admin/ directory via HTTP/HTTPS from the web server. Check if the reservation.php endpoint is reachable.Affected if The /admin/reservation.php endpoint is accessible over the network.
-
Inspect the email parameter handling in codeOpen /admin/reservation.php and locate the code handling the 'email' parameter. Look for SQL queries that use this parameter without prepared statements, parameter binding, or input sanitization.Affected if The email parameter is used in a SQL query without prepared statements, parameterized queries, or input validation/sanitization.
A defender is affected if Responsive Hotel Site 1.0 is installed with the /admin/reservation.php file accessible and the email parameter handled without parameterized queries in the code.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace dynamic SQL queries with prepared statements/parameterized queries, implement input validation on the email parameter, and apply the principle of least privilege to database accounts.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12856 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-12856 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data