dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2024-53544

CRITICAL · 9.8 CVSS v3.1 Published 2025-02-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
NovaCHRON Zeitsysteme GmbH & Co. KG Smart Time Plus v8.x to v8.6 was discovered to contain a SQL injection vulnerability via the getCookieNames method in the smarttimeplus/MySQLConnection endpoint.

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 confidence

SQL injection vulnerability in the getCookieNames method of the smarttimeplus/MySQLConnection endpoint in NovaCHRON Smart Time Plus v8.x through v8.6 allows remote unauthenticated attackers to inject malicious SQL queries via the cookie name parameter.

MitigationUpgrade to version beyond v8.6 once available, or apply vendor-supplied patch; implement parameterized queries and input validation as immediate compensating controls.

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify NovaCHRON Smart Time Plus installation
    Locate the NovaCHRON Smart Time Plus application installation directory or check running services for 'smarttimeplus' or 'NovaCHRON' processes
    Affected if The software is installed on the system
  2. Determine installed version
    Check the application's version information (typically found in about dialog, version file, or installation metadata) and compare against the affected range v8.x through v8.6
    Affected if Installed version is v8.x through v8.6 inclusive
  3. Verify MySQLConnection endpoint exposure
    Check if the smarttimeplus/MySQLConnection endpoint is accessible on the application server (typically via HTTP/HTTPS access to the web interface)
    Affected if The MySQLConnection endpoint is externally or internally accessible
  4. Confirm MySQL database configuration
    Inspect the application's database configuration to verify it uses MySQL as the backend database
    Affected if The application is configured to connect to a MySQL database

The environment is affected if NovaCHRON Smart Time Plus v8.x through v8.6 is installed, the smarttimeplus/MySQLConnection endpoint is accessible, and the application uses MySQL as its backend database.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version beyond v8.6 once available, or apply vendor-supplied patch; implement parameterized queries and input validation as immediate compensating controls.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA6.0 h
36.0 hours of engineering $6,360
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-53544 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-53544 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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