Stored XSS on entire Client site in fossbilling/fossbilling

Valid

Reported on

Jun 15th 2023


Description

Admin or Staff with "System" permission can produce a store XSS on entire Client site

Proof of Concept

Edit the "Signature" field to this value "FOSSBilling.org - Client Management, Invoice and Support Software"><img src=x onerror=alert(document.domain)>" image

Then it will trigger in every Client screens image

Seems like it was rendered to the footer image

Impact

Since the cookie used for sessions was set with the "HTTPonly" attribute, so the attacker can not hijack user sessions but still can carry out some malicious actions by manipulating XSS vulnerabilities, such as:

  • Users are being redirected to a malicious website.
  • Capturing keystrokes from users.
  • Obtaining access to a user’s browsing history and clipboard contents.
  • Execution of web browser-based exploits (e.g., crashing the browser).
  • Influencing the users to submit requests to a server controlled by the attacker.
  • Modifying the page’s content.
  • Using deception to trick the victim into disclosing their password to the application or other applications.
  • Using a security vulnerability in the web browser, infecting the victim with other malicious code, and potentially taking over the victim’s computer.
We are processing your report and will contact the fossbilling team within 24 hours. 3 months ago
hiu240900 modified the report
3 months ago
hiu240900 modified the report
3 months ago
Belle Aerni validated this vulnerability 3 months ago

Fixed here : https://github.com/FOSSBilling/FOSSBilling/pull/1338

hiu240900 has been awarded the disclosure bounty
The fix bounty is now up for grabs
The researcher's credibility has increased: +7
Belle Aerni marked this as fixed in 0.5.1 with commit f5df51 3 months ago
Belle Aerni has been awarded the fix bounty
This vulnerability will not receive a CVE
This vulnerability is scheduled to go public on Jul 3rd 2023
hiu240900
3 months ago

Researcher


@maintainer I forgot about this one, could you please also assign a CVE for this report?

Thanks!

hiu240900
3 months ago

Researcher


@bellenottelling

Belle Aerni
3 months ago

Maintainer


This report will not be receiving a CVE

hiu240900
3 months ago

Researcher


can I know the reason why?

Belle Aerni
3 months ago

Maintainer


Sure, It's not receiving a CVE for a two primary reasons: 1: It's just barely a medium severity at 4.3 2: It has to be exploited by somebody who is trusted enough within the company or organization to have permissions within FOSSBilling that would allow them to modify company information such as the phone number, mailing address, email address, or even the terms of service. (This is the primary reason)

While this is a valid vulnerability and has been marked and resolved as such, someone with the permissions required to exploit it could still potentially do significant damage without the XSS vulnerability existing simply as a result of what the system administrator has given them access to.

Belle Aerni published this vulnerability 3 months ago
to join this conversation