Skip to content

Cross-site scripting (XSS) vulnerability in Description metadata

Moderate severity GitHub Reviewed Published Jun 7, 2024 in getformwork/formwork • Updated Jun 7, 2024

Package

composer getformwork/formwork (Composer)

Affected versions

< 1.13.1
= 2.0.0-beta.1

Patched versions

1.13.1

Description

Summary

Regardless of the role or privileges, no user should be able to inject malicious JavaScript (JS) scripts into the body HTML. an XSS (Cross-Site Scripting) vulnerability, specifically a Stored XSS, which affects all pages of the website. Once the JS script is embedded in the body HTML, the XSS will trigger on any page a victim visits, such as the about, blog, contact, or any other pages, except for the panel.

Impact

This vulnerability allows attackers to inject malicious JS or HTML through a crafted payload into the vulnerable spot, achieving persistence and attacking numerous visitors or anyone accessing the website. The attack can be widespread and affect many users because the malicious JS will execute on every page, unlike an injection on a specific page (e.g., injecting on the About page would only affect that page). In this case, a single injection point leads to the execution of the malicious JS on all pages.

Patches

Details

An attackers (requires administrator privilege) to execute arbitrary web scripts by modifying site options via /panel/options/site. This type of attack is suitable for persistence, affecting visitors across all pages (except the dashboard).

PoC

  1. Log in with an Administrator user account.
  2. Navigate to /panel/options/site/.
  3. Inject the JS script by adding to the description field.
  4. Simulate a victim who is not a site member visiting the website. You will notice that the JS script executes on every page they vis

image
image
image
image

References

@giuscris giuscris published to getformwork/formwork Jun 7, 2024
Published by the National Vulnerability Database Jun 7, 2024
Published to the GitHub Advisory Database Jun 7, 2024
Reviewed Jun 7, 2024
Last updated Jun 7, 2024

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
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:R/S:C/C:L/I:L/A:N

EPSS score

0.051%
(21st percentile)

Weaknesses

CVE ID

CVE-2024-37160

GHSA ID

GHSA-5pxr-7m4j-jjc6

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.