CVE-2026-3958
Server-Side Request Forgery in Woahai321 ListSync JSON Handler
Publication date: 2026-03-11
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| woahai321 | listsync | to 0.6.6 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-918 | The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Woahai321 ListSync software up to version 0.6.6, specifically in the requests.post function within the list-sync-main/api_server.py file of the JSON Handler component.
The issue allows an attacker to perform server-side request forgery (SSRF), meaning the attacker can make the server send unauthorized requests to other internal or external systems.
The attack can be carried out remotely, and the exploit has been publicly disclosed. The project was informed early but has not yet responded.
How can this vulnerability impact me? :
This vulnerability can allow an attacker to make the vulnerable server send unauthorized requests to other systems, potentially accessing internal resources or services that are not normally exposed.
Such unauthorized requests could lead to information disclosure, unauthorized actions on internal systems, or further exploitation depending on the internal network configuration.
Because the attack can be performed remotely, it increases the risk of exploitation without physical access.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know