# CVE-2024-55507: Privilege escalation in n/a

> A remote attacker can escalate privileges in the CodeAstro Complaint Management System via the delete_e.php component.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jan 2025
- **Updated:** 3 Jan 2025
- **Also known as:** GHSA-h735-q6rm-hjcj

## What is CVE-2024-55507?

CVE-2024-55507 is a critical vulnerability in n/a, published on 3 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in CodeAstro Complaint Management System v.1.0 allows a remote attacker to escalate privileges via the delete_e.php component.

Weakness: CWE-281 (Improper Preservation of Permissions)

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

It affects 1 product.


Products: Codeastro Complaint Management System.

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

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

## Is CVE-2024-55507 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-55509](https://insights.sbomify.com/CVE-2024-55509/): SQL injection in n/a (critical 9.8)
- [CVE-2024-55505](https://insights.sbomify.com/CVE-2024-55505/): Code injection in n/a (high 8.8)
- [CVE-2024-55506](https://insights.sbomify.com/CVE-2024-55506/): Missing authorization in n/a (high 8.8)
- [CVE-2024-56889](https://insights.sbomify.com/CVE-2024-56889/): Missing authorization in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-55507 is a critical vulnerability in n/a, published on 3 Jan 2025. 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-55507 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-55507/ (Markdown: https://insights.sbomify.com/CVE-2024-55507/index.md)
```

## Sources

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

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