VulnerabilityPublished 10 Oct 2025

CVE-2025-62292: SonarSource SonarQube · Incorrect Resource Transfer Between Spheres

Affects SonarSource SonarQubeSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

4.3Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within 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 10 Oct 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
SonarSource SonarQube	Affected =2025.1	Fixed in–

AI-suggested

To mitigate CVE-2025-62292, organizations should prioritize upgrading SonarQube to versions 25.6, 2025.3 Commercial, or 2025.1.3 LTA or later once patches are released. Until then, restrict access to the /api/v2/users-management/users endpoint by implementing strict role-based access controls and network segmentation to limit API access only to trusted administrators. Review and audit user privileges regularly to minimize the number of low-privileged users with access to the system. Employ multi-factor authentication (MFA) to reduce the risk of credential compromise. Monitor API usage logs for unusual access patterns that could indicate exploitation attempts. Additionally, educate users about phishing risks and implement email filtering solutions to detect and block targeted phishing campaigns. Consider deploying Web Application Firewalls (WAFs) with custom rules to block unauthorized API calls. Finally, maintain an incident response plan that includes procedures for handling data exposure incidents and GDPR notification requirements.

Description

In SonarQube before 25.6, 2025.3 Commercial, and 2025.1.3 LTA, authenticated low-privileged users can query the /api/v2/users-management/users endpoint and obtain user fields intended for administrators only, including the email addresses of other accounts.

Impact

For European organizations, the primary impact is the unauthorized disclosure of user email addresses within SonarQube instances. This can lead to privacy violations under GDPR, as email addresses are personal data. Attackers could use this information to conduct spear-phishing campaigns targeting developers and administrators, potentially leading to credential theft or further compromise. While the vulnerability does not directly affect system integrity or availability, the indirect risks from social engineering and insider threats are significant. Organizations relying heavily on SonarQube for code quality and security analysis may face reputational damage if user data is leaked. Additionally, compliance risks arise due to inadequate protection of personal data. The vulnerability is particularly concerning in environments where low-privileged users are numerous or where credential compromise is more likely. The lack of known exploits reduces immediate risk but does not eliminate the threat, especially as the vulnerability is publicly disclosed.

References

sonarsource.atlassian.net/browse/SONAR-24830 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Oct 2025, 06:39 UTC

WeaknessesCWE-669

Technical details

References

Community reviews

Related threats