CVE-2023-27666
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 · uneditedAuto Dealer Management System v1.0 was discovered to contain a cross-site scripting (XSS) vulnerability via the name parameter at /classes/SystemSettings.php?f=update_settings.
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 confidenceAuto Dealer Management System v1.0 contains a stored cross-site scripting (XSS) vulnerability in the name parameter at /classes/SystemSettings.php?f=update_settings. The application fails to properly sanitize user input before storing and displaying it, allowing attackers to inject malicious JavaScript that executes in the browsers of other users who view the affected settings page.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Verify Auto Dealer Management System versionLocate the version file, about page, or admin dashboard showing the software version. Common paths include /about.php, /admin/, or a config/version file. Compare the installed version to the affected range (1.0).Affected if The installed version is exactly 1.0
-
Confirm the vulnerable file existsCheck if the file /classes/SystemSettings.php exists in the web root. This is the file containing the vulnerable update_settings function.Affected if The file /classes/SystemSettings.php exists on the server
-
Inspect the update_settings function for input sanitizationOpen /classes/SystemSettings.php and locate the function handling the 'name' parameter from the update_settings action. Look for whether the $_POST['name'] value is passed through sanitization functions like htmlspecialchars(), strip_tags(), or a whitelist before storing it.Affected if The 'name' parameter is stored without sanitization (no htmlspecialchars, strip_tags, or equivalent) in the update_settings function
-
Check how the name value is displayed in the settings pageFind where the 'name' value is retrieved and displayed in the admin settings page. This could be in the main settings page or a related view file. Verify if output encoding is applied when rendering the name value in HTML context.Affected if The name value is displayed in HTML without htmlspecialchars() or equivalent output encoding
You are affected if you are running version 1.0 of Auto Dealer Management System and the code shows the 'name' parameter is stored and displayed without sanitization and encoding respectively.
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 dataImplement input validation and output encoding for the name parameter. Use htmlspecialchars() or equivalent sanitization functions when displaying the name value to prevent script execution.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-27666 — 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-27666 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