# CVE-2024-55232: Missing authorization in n/a

> Attackers can delete other users' notes due to missing authorization checks in the notes management module.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Dec 2024
- **Updated:** 26 Dec 2024
- **Also known as:** GHSA-vpfg-w257-rq9f

## What is CVE-2024-55232?

CVE-2024-55232 is a medium-severity missing authorization vulnerability in n/a, published on 18 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An IDOR vulnerability in the manage-notes.php module in PHPGurukul Online Notes Sharing Management System v1.0 allows unauthorized users to delete notes belonging to other accounts due to missing authorization checks. This flaw enables attackers to delete another user's information.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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

It affects 1 product.


Products: Phpgurukul Online Notes Sharing Management System.

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

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

## Is CVE-2024-55232 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-55231](https://insights.sbomify.com/CVE-2024-55231/): Missing authorization in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-55232 is a medium-severity missing authorization vulnerability in n/a, published on 18 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-55232 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-55232/ (Markdown: https://insights.sbomify.com/CVE-2024-55232/index.md)
```

## Sources

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

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