CVE-2025-23911
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in solidres Solidres – Hotel booking plugin solidres allows SQL Injection.This issue affects Solidres – Hotel booking plugin: from n/a through <= 0.9.4.
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 · moderate confidenceSQL Injection vulnerability in the Solidres hotel booking plugin allows attackers to inject malicious SQL commands through unsanitized user inputs. The flaw affects all versions up to and including 0.9.4, potentially enabling unauthorized database access, data exfiltration, or manipulation of booking records.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L
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 the installed Solidres plugin versionAccess your CMS admin panel (WordPress/Joomla) and navigate to the plugins section to view the installed version of the Solidres hotel booking plugin, or check the plugin's version file if you have file system accessAffected if The installed version is 0.9.4 or any earlier version (e.g., 0.9.3, 0.9.2, 0.8.x)
-
Confirm the plugin is activeVerify that the Solidres hotel booking plugin is currently enabled on your website through the CMS plugin management interfaceAffected if The plugin is active and serving booking functionality to users
-
Identify SQL injection entry pointsReview the booking forms and user input fields in the Solidres plugin (such as guest name, email, phone, and booking request fields) where user-supplied data is processedAffected if User input fields exist and accept data without visible sanitization indicators
-
Check for SQL injection indicators in logsReview your web server logs and database logs for unusual SQL syntax patterns, error messages containing SQL keywords (SELECT, UNION, INSERT), or database authentication errors originating from booking-related requestsAffected if Suspicious SQL-like patterns appear in logs from booking form submissions
Your environment is affected if the Solidres hotel booking plugin version is 0.9.4 or earlier and the plugin is active, exposing user input fields that could be exploited for SQL injection.
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 dataUpdate to the latest patched version of Solidres hotel booking plugin. If no patch is available, audit code for parameterized queries and implement input validation/sanitization on all user-supplied data before SQL execution.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23911 — 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-23911 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