CVE-2023-21412
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 · uneditedUser provided input is not sanitized on the AXIS License Plate Verifier specific “search.cgi” allowing for SQL injections.
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 search.cgi component of AXIS License Plate Verifier allows remote attackers to inject malicious SQL queries through unsanitized user input.
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<= 2.8.3CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 Axis License Plate Verifier installationLocate the Axis License Plate Verifier application on the system. This is typically a web-based application running on an Axis network device or server. Check the web interface or system inventory for this product.Affected if Axis License Plate Verifier is present on the network or system.
-
Identify installed versionAccess the admin interface of Axis License Plate Verifier and navigate to the version or about section. Alternatively, check system documentation or the Axis device webpage for the software version information.Affected if The installed version is 2.8.3 or any earlier version.
-
Locate search.cgi componentIdentify if search.cgi is accessible on the web server. This is typically found at a path like /cgi-bin/search.cgi or similar within the application directory structure. Check the application's web directory for this file.Affected if The search.cgi file exists and is accessible via HTTP/HTTPS on the network.
-
Verify unsanitized input handlingReview or intercept requests to search.cgi to determine if user-supplied input (such as search parameters) is passed directly to SQL queries without apparent sanitization or use of parameterized queries. Test by observing how search parameters are processed.Affected if User input from search parameters is used in SQL queries without proper sanitization or parameterized queries.
The environment is affected if Axis License Plate Verifier version 2.8.3 or earlier is installed and the search.cgi component with unsanitized user input is accessible and processing search queries.
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 proper input validation and use parameterized queries (prepared statements) in search.cgi to prevent SQL injection attacks. Apply vendor patches when available.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-21412 — 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-21412 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