dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2024-53543

MEDIUM · 5.4 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 →
60/100
Remediation priority · Elevated
Remotely reachable 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 addProject 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 NovaCHRON Smart Time Plus v8.x to v8.6 allows injection through the addProject method in the smarttimeplus/MySQLConnection endpoint. The vulnerability stems from unsanitized user input being incorporated directly into SQL queries.

MitigationReplace dynamic SQL queries with parameterized queries or prepared statements in the addProject method to prevent SQL injection. Validate and sanitize all user inputs before using them in database operations.

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
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 checks

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

  1. Confirm NovaCHRON Smart Time Plus installation
    Locate the NovaCHRON Smart Time Plus application installation directory or check running services/processes for the product
    Affected if The product is not installed or not present in the environment
  2. Determine installed version
    Check the application version through its UI, configuration files, or installation metadata
    Affected if The version falls within v8.x to v8.6 (any version from 8.0 through 8.6)
  3. Locate the MySQLConnection endpoint
    Inspect the application web directory or API configuration files for the smarttimeplus/MySQLConnection endpoint
    Affected if The MySQLConnection endpoint exists and is accessible via the application
  4. Verify addProject method exposure
    Review application routing or endpoint mappings to confirm the addProject method is exposed and callable
    Affected if The addProject method is enabled and accessible via HTTP/soap requests to the MySQLConnection endpoint
  5. Inspect SQL query implementation
    If source code or decompiled classes are available, examine the addProject method for direct string concatenation of user input into SQL queries
    Affected if User-supplied parameters are concatenated directly into SQL statements without parameterization or input sanitization

The environment is affected if NovaCHRON Smart Time Plus v8.x to v8.6 is installed with the smarttimeplus/MySQLConnection endpoint and accessible addProject method that uses unsanitized input in SQL queries.

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

Replace dynamic SQL queries with parameterized queries or prepared statements in the addProject method to prevent SQL injection. Validate and sanitize all user inputs before using them in database operations.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-53543 — 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-53543 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