CVE-2023-43375
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 · uneditedHoteldruid v3.0.5 was discovered to contain multiple SQL injection vulnerabilities at /hoteldruid/clienti.php via the annonascita, annoscaddoc, giornonascita, giornoscaddoc, lingua_cli, mesenascita, and mesescaddoc parameters.
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 confidenceHoteldruid v3.0.5 contains multiple SQL injection vulnerabilities in /hoteldruid/clienti.php via seven parameters (annonascita, annoscaddoc, giornonascita, giornoscaddoc, lingua_cli, mesenascita, mesescaddoc) that handle client date-of-birth and language data. With a CVSS 9.8 rating, these unauthenticated SQL injection flaws could allow attackers to exfiltrate data, escalate privileges, or compromise the underlying database server.
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= 3.0.5CVSS 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.
-
Confirm Hoteldruid installationIdentify the web application by checking for Hoteldruid files, banners, or application identifiers in the web root or server responseAffected if Hoteldruid is present in the environment
-
Determine installed versionLocate version information in Hoteldruid files (such as version.php, about.php, or configuration files in the /hoteldruid directory) and compare to 3.0.5Affected if The installed version is exactly 3.0.5
-
Verify clienti.php existsCheck for the presence of /hoteldruid/clienti.php in the web application directory structureAffected if The vulnerable clienti.php file exists in the expected location
-
Assess parameter exposureInspect HTTP requests to clienti.php and verify if the seven parameters (annonascita, annoscaddoc, giornonascita, giornoscaddoc, lingua_cli, mesenascita, mesescaddoc) are accepted as user input via GET or POSTAffected if The application accepts and processes these seven parameters without parameterized queries
-
Confirm client data processing is enabledVerify that the client management feature in Hoteldruid is active, as this triggers the vulnerable code path in clienti.php that processes date-of-birth and language fieldsAffected if The client registration or management functionality is enabled and accessible
The environment is affected if Hoteldruid version 3.0.5 is installed, the clienti.php file exists, and the client management feature exposing the seven vulnerable parameters (annonascita, annoscaddoc, giornonascita, giornoscaddoc, lingua_cli, mesenascita, mesescaddoc) is accessible.
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 dataUpgrade to a patched version of Hoteldruid; if unavailable, refactor the affected clienti.php file to use parameterized queries/prepared statements for all seven vulnerable parameters, apply strict input validation, and consider deploying a WAF as a temporary mitigation.
- Consultation3.0 h
- Implementation8.0 h
- Testing6.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,568.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-43375 — 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-2023-43375 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