# CVE-2024-28279: SQL injection in n/a

> An attacker can execute arbitrary SQL commands via the bookisbn parameter in the Computer Book Store web application.

- **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:** 13 May 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-q2g7-qm59-84wp

## What is CVE-2024-28279?

CVE-2024-28279 is a high-severity SQL injection vulnerability in n/a, published on 13 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Code-projects Computer Book Store 1.0 is vulnerable to SQL Injection via book.php?bookisbn=.

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

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

It affects 1 product.


Products: Carmelo Computer Book Store.

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

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

## Is CVE-2024-28279 being exploited?

There is no known exploitation of CVE-2024-28279 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2025-69559](https://insights.sbomify.com/CVE-2025-69559/): File upload in n/a (critical 9.8)
- [CVE-2024-24100](https://insights.sbomify.com/CVE-2024-24100/): SQL injection in n/a (high 8.3)
- [CVE-2024-24096](https://insights.sbomify.com/CVE-2024-24096/): SQL injection in n/a (high 7.8)
- [CVE-2025-14647](https://insights.sbomify.com/CVE-2025-14647/): code-projects Computer Book Store admin_delete.php sql injection (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-28279 is a high-severity SQL injection vulnerability in n/a, published on 13 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-28279 in the wild and no public exploit code.

Affected product: n/a. 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-28279/ (Markdown: https://insights.sbomify.com/CVE-2024-28279/index.md)
```

## Sources

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

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