# CVE-2024-12125: 3scale-porta: readonly fields not validated server-side

> Attackers can modify restricted read-only or hidden account fields in the 3scale Developer Portal due to missing server-side validation.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 6 Nov 2025
- **Updated:** 24 Dec 2025
- **Also known as:** GHSA-7fc5-p6pg-8vrj

## What is CVE-2024-12125?

CVE-2024-12125 is a high-severity missing authorization vulnerability in Red Hat 3scale API Management Platform 2, published on 6 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was found in the 3scale Developer Portal. When creating or updating an account in the Developer Portal UI it is possible to modify fields explicitly configured as read-only or hidden, allowing an attacker to modify restricted information.

Weakness: CWE-281 (Improper Preservation of Permissions)

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


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

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

## Is CVE-2024-12125 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-12125 is a high-severity missing authorization vulnerability in Red Hat 3scale API Management Platform 2, published on 6 Nov 2025. 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-12125 in the wild and no public exploit code.

Affected product: Red Hat 3scale API Management Platform 2. 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-12125/ (Markdown: https://insights.sbomify.com/CVE-2024-12125/index.md)
```

## Sources

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

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