# CVE-2023-2544: Authorization Bypass on UPV PEIX

> Authenticated users can bypass authorization to retrieve other users' stored information by manipulating the ID parameter in a POST request.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Oct 2023
- **Updated:** 19 Sep 2024
- **Also known as:** GHSA-c538-9356-xgvr

## What is CVE-2023-2544?

CVE-2023-2544 is a medium-severity missing authorization vulnerability in Universitat Politècnica de València (UPV) UPV PEIX, published on 3 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Authorization bypass vulnerability in UPV PEIX, affecting the component "pdf_curri_new.php". Through a POST request, an authenticated user could change the ID parameter to retrieve all the stored information of other registered users.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2023-2544?

It affects 1 product.


Products: Upv Peix.

## How do I fix CVE-2023-2544?

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

## Is CVE-2023-2544 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-2544 and fix it if it is affected.

What it is: CVE-2023-2544 is a medium-severity missing authorization vulnerability in Universitat Politècnica de València (UPV) UPV PEIX, published on 3 Oct 2023. 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-2023-2544 in the wild and no public exploit code.

Affected product: Universitat Politècnica de València (UPV) UPV PEIX. 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-2023-2544/ (Markdown: https://insights.sbomify.com/CVE-2023-2544/index.md)
```

## Sources

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

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