# CVE-2024-2014: Panabit Panalog sprog_upstatus.php sql injection

> Remote attackers can exploit SQL injection in Panabit Panalog to read or modify database contents via the id parameter.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Feb 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-2c52-g67x-6vf3

## What is CVE-2024-2014?

CVE-2024-2014 is a high-severity SQL injection vulnerability in Panabit Panalog, published on 29 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability classified as critical was found in Panabit Panalog 202103080942. This vulnerability affects unknown code of the file /Maintain/sprog_upstatus.php. The manipulation of the argument id leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-255268. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2024-2014?

It affects 1 product.


Products: Panabit Panalog.

## How do I fix CVE-2024-2014?

No fix has been published for CVE-2024-2014 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-2014 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-2014 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-2014 and fix it if it is affected.

What it is: CVE-2024-2014 is a high-severity SQL injection vulnerability in Panabit Panalog, published on 29 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-2014 exists.

Affected product: Panabit Panalog. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-2014/ (Markdown: https://insights.sbomify.com/CVE-2024-2014/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-2014
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-2014
- OSV: https://osv.dev/vulnerability/CVE-2024-2014

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-2014/
Summaries are generated and may contain mistakes; the official description above is the record.