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

> Attackers can inject SQL commands via the dev_code parameter in BigAnt Office Messenger to read or modify database contents.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Jan 2025
- **Updated:** 10 Jan 2025
- **Also known as:** GHSA-2wf3-32wx-c338

## What is CVE-2024-54761?

CVE-2024-54761 is a medium-severity SQL injection vulnerability in n/a, published on 9 Jan 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

BigAnt Office Messenger 5.6.06 is vulnerable to SQL Injection via the 'dev_code' parameter.

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

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

It affects 1 product.


Products: Bigantsoft Bigant Office Messenger 5.

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

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

## Is CVE-2024-54761 being exploited?

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

Public exploit code:

- CVE-2024-54761 PoC (github_poc): https://github.com/nscan9/CVE-2024-54761
- BigAnt Office Messenger 5.6.06 - SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2021-43430](https://insights.sbomify.com/CVE-2021-43430/): File upload in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-54761 is a medium-severity SQL injection vulnerability in n/a, published on 9 Jan 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-54761 exists.

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-54761/ (Markdown: https://insights.sbomify.com/CVE-2024-54761/index.md)
```

## Sources

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

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