VulnerabilityPublished 17 Dec 2025

CVE-2025-67285: Lonlydance · SQL Injection

Affects LonlydanceSource CVE Database V5

Not known to be exploited · CVSS 7.3 High.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score

7.3High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubbardminx/Lonlydance`pkg:github/bardminx/Lonlydance`Other threats	Affected =1.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Immediate mitigation should focus on implementing robust input validation and sanitization for the 'id' parameter to prevent injection of malicious SQL code. Employ parameterized queries or prepared statements to separate code from data, effectively neutralizing injection attempts. Conduct a thorough code audit of all database interactions within the application to identify and remediate similar vulnerabilities. If a patch from the vendor becomes available, prioritize its deployment. In the interim, consider deploying web application firewalls (WAFs) with SQL injection detection rules tailored to the application's traffic patterns. Monitor logs for unusual query patterns or repeated access attempts to the vulnerable endpoint. Restrict access to the administrative interface using network segmentation and strong authentication controls to reduce exposure. Educate development teams on secure coding practices to prevent future injection flaws. Finally, maintain regular backups and incident response plans to quickly recover from potential compromises.

Description

CVE-2025-67285 is a high-severity SQL injection vulnerability found in the '/cts/admin/? page=zone' endpoint of ITSourcecode COVID Tracking System Using QR-Code v1.0. The flaw arises because the 'id' parameter is used directly in SQL queries without proper sanitization or validation, allowing attackers to inject malicious SQL code. This vulnerability can be exploited remotely without authentication or user interaction, potentially leading to unauthorized data disclosure, data modification, or denial of service. Although no known exploits are currently reported in the wild, the vulnerability poses a significant risk to organizations using this system. European organizations relying on this COVID tracking system could face data breaches or operational disruptions. Mitigation requires immediate input validation, parameterized queries, and code review. Countries with higher adoption of this specific COVID tracking system and critical public health infrastructure are at greater risk. The CVSS score of 7.

Impact

For European organizations, especially those involved in public health and pandemic response, this vulnerability could lead to severe consequences. Exploitation could result in unauthorized access to sensitive personal health information collected by the COVID tracking system, violating privacy regulations such as GDPR. Data integrity could be compromised, leading to inaccurate tracking data and undermining public health efforts. Availability impacts could disrupt the system's operation, affecting contact tracing and containment measures. The potential for remote exploitation without authentication increases the risk of widespread attacks. Organizations relying on this system may face reputational damage, regulatory penalties, and operational setbacks. Given the critical role of COVID tracking systems in managing public health crises, ensuring their security is paramount to maintaining trust and effectiveness.

Summary

CVE-2025-67285 identifies a SQL injection vulnerability in the ITSourcecode COVID Tracking System Using QR-Code v1.0, specifically within the '/cts/admin/?page=zone' file. The vulnerability stems from the unsafe handling of the 'id' parameter, which is incorporated directly into SQL statements without proper sanitization or validation. This lack of input validation allows an attacker to craft malicious SQL payloads that can manipulate the backend database queries. Exploitation does not require authentication or user interaction, making it remotely exploitable over the network. Potential attack vectors include unauthorized data retrieval, modification, or deletion, which can compromise confidentiality, integrity, and availability of the system's data. The vulnerability is classified under CWE-89 (SQL Injection), a well-known and critical web application security flaw. The CVSS v3.1 base score of 7.3 indicates a high severity, with attack vector as network (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), and impacts on confidentiality, integrity, and availability (C:L/I:L/A:L). Although no public exploits have been reported yet, the vulnerability's characteristics make it a prime target for attackers aiming to disrupt COVID tracking operations or steal sensitive health data. The absence of patch links suggests that a fix might not yet be available, emphasizing the need for immediate mitigation efforts.

CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #2OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Parameterization
If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.
Architecture and Design · Operation · Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment.
OWASP Cheat Sheets
Query Parameterization (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.4 (opens in a new tab)
V5.3.5 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
Command Line Execution through SQL Injection (opens in a new tab)
Object Relational Mapping Injection (opens in a new tab)
SQL Injection through SOAP Parameter Tampering (opens in a new tab)
Expanding Control over the Operating System from the Database (opens in a new tab)
SQL Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/bardminx/Lonlydance/issues/1 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Dec 2025, 17:06 UTC

WeaknessesCWE-89

Technical details

References

Community reviews

Related threats