Skip to content

Authenticated XSS in "Publish Key" Field Allowing Unauthorized Administrator User Creation

Moderate
jack7anderson7 published GHSA-8rw6-g96j-3w7m Nov 5, 2024

Package

SuiteCRM

Affected versions

<=7.14.4
<=8.6.1

Patched versions

7.14.6
8.7.1

Description

Summary

The "Publish Key" field in SuiteCRM's Edit Profile page is vulnerable to Reflected Cross-Site Scripting (XSS), allowing an attacker to inject malicious JavaScript code. This can be exploited to steal CSRF tokens and perform unauthorized actions, such as creating new administrative users without proper authentication.

Details

The vulnerability arises due to insufficient input validation and sanitization of the Publish Key field within the SuiteCRM application. When an attacker injects a malicious script, it gets executed within the context of an authenticated user's session. The injected script (o.js) then leverages the captured CSRF token to forge requests that create new administrative users, effectively compromising the integrity and security of the CRM instance.

Impact

This vulnerability is a critical Cross-Site Scripting (XSS) issue. Its impact includes:

  1. Unauthorized Administrative Access: An attacker can create new administrative users, potentially gaining complete control over the CRM instance.
  2. CSRF Token Theft: Allows for unauthorized actions to be performed on behalf of authenticated users.
  3. Data Integrity Compromise: The ability to manipulate user accounts and settings can lead to data loss, leakage, or unauthorized modification.

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

CVE ID

CVE-2024-50335

Weaknesses

Credits