Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-37fq-47qj-6j5j
No affected components available
Summary
A stored and blind XSS vulnerability exists in the form title field. A malicious attacker can inject JavaScript without any authentication via a form title that is saved in the backend database. When any user visits that injected page, the JavaScript payload gets executed.
Type: Stored and Blind Cross-Site Scripting (XSS) Affected Component: form title input field Authentication Required: No (Unauthenticated attack possible) Impact: Arbitrary JavaScript execution in victim’s browser
Details
A Stored XSS vulnerability occurs when an application stores malicious user input (in this case, a script injected via the form title field) in its backend database and renders it later on a page viewed by other users without proper sanitization or encoding.
In this case, the attacker can inject JavaScript payloads in the title field of a form, which the application stores in the database. When any user, such as an admin or another visitor, views the page that displays this title, the malicious script executes in their browser context.
PoC
- Visit
https://yeswiki.net/?BazaR&vue=formulaireorlocalhost/?BazaR&vue=formulaireorhttps://ferme.yeswiki.net/[username]/?BazaR&vue=formulaire - Click on the
+icon to add a record via theDiaryform. - Inject the payload like:
<script>alert(document.cookie)</script>or<script>alert(1)</script>intoName of the eventandDescription - Then save the record by clicking
To validate - The payload will be executed when anyone visits
/?BazaR&vue=consulteralso in the diary record/?wiki=BazaR&vue=consulter&action=recherche&q=&id=2&facette=
The payload is persistant.
The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker does not need any special privileges or access rights.
Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard