VulnerabilityPublished 6 Nov 2025Updated 24 Dec 2025

CVE-2024-12125: 3scale porta · Improper Preservation of Permissions

Affects 3scale portaSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
3scale porta	Affected =0	Fixed in–

AI-suggested

Immediately restrict network access to the 3scale Developer Portal UI to trusted administrators only, using network segmentation, VPNs, or IP whitelisting.
Implement strict monitoring and logging of all account creation and update activities within the Developer Portal to detect unauthorized modifications promptly.
Review and harden role-based access controls (RBAC) within the portal to minimize permissions granted to users and administrators.
Coordinate with the 3scale vendor or Red Hat for official patches or updates addressing CVE-2024-12125 and apply them as soon as they become available.
Conduct a thorough audit of existing accounts and configurations to identify and remediate any unauthorized changes made prior to mitigation.
Educate administrators and developers about this vulnerability and enforce security best practices when managing API developer portals.
Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block anomalous requests attempting to modify read-only or hidden fields.
Regularly update and patch all components of the API management infrastructure to reduce exposure to similar vulnerabilities.

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.

Impact

The primary impact of CVE-2024-12125 is on the integrity of the 3scale Developer Portal environment. Attackers exploiting this vulnerability can modify restricted fields that should be immutable or hidden, potentially altering user roles, permissions, or API configurations. This could lead to unauthorized privilege escalation, manipulation of API access controls, or disruption of API management workflows. Organizations relying on 3scale porta for managing developer accounts and API gateways may face risks of unauthorized changes that compromise their API security posture. Although confidentiality and availability are not directly affected, the integrity breach can cascade into broader security issues, including unauthorized data access or service misuse. The vulnerability's remote exploitability without authentication increases the risk of widespread attacks if left unmitigated. The lack of known exploits currently provides a window for organizations to prepare defenses before active exploitation occurs.

References

Community reviews

Loading reviews…