CVE-2026-4623
Server-Side Request Forgery in Jeson CRM API Module
Publication date: 2026-03-24
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 |
|---|---|---|
| defaultfuction | jeson-customer-relationship-management-system | to 1b4679c4d06b90d31dd521c2b000bfdec5a36e00 (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?
[{'type': 'paragraph', 'content': 'This vulnerability is a Server-Side Request Forgery (SSRF) found in the Jeson Customer Relationship Management System, specifically in the API endpoint /api/System.php. It occurs because the application accepts a URL parameter from an HTTP GET request and uses it directly to make server-side requests without proper validation or sanitization.'}, {'type': 'paragraph', 'content': "An attacker can manipulate the 'url' argument to make the server send crafted requests to arbitrary internal or external destinations. This means the attacker can cause the server to access unintended resources, potentially including internal network services or local files."}] [1, 3]
How can this vulnerability impact me? :
The SSRF vulnerability allows remote attackers to exploit the server to perform unauthorized requests to internal or external systems. This can lead to several serious impacts:
- Scanning internal networks to discover services not exposed publicly.
- Accessing internal web interfaces or administrative panels that are otherwise protected.
- Reading sensitive internal files, such as system files like /etc/passwd.
- Using the server as a pivot point to attack other internal or external systems.
Overall, this can lead to information disclosure, internal system compromise, and broader network intrusions.
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?
[{'type': 'paragraph', 'content': 'This vulnerability can be detected by monitoring HTTP requests to the API endpoint /api/System.php, specifically looking for requests that include the url GET parameter. Since the vulnerability involves server-side request forgery (SSRF), suspicious outbound requests originating from the server to unexpected or internal destinations may indicate exploitation attempts.'}, {'type': 'paragraph', 'content': 'To detect potential exploitation, you can analyze web server logs for requests to /api/System.php with the url parameter set to unusual or internal addresses.'}, {'type': 'paragraph', 'content': 'Example commands to detect such activity include:'}, {'type': 'list_item', 'content': 'Using grep to find suspicious requests in web server logs: grep "/api/System.php?url=" /var/log/apache2/access.log'}, {'type': 'list_item', 'content': 'Using curl to test the endpoint with a controlled URL parameter: curl -v "http://yourserver/api/System.php?url=http://example.com"'}, {'type': 'list_item', 'content': 'Monitoring outbound network connections from the server to unexpected IPs or protocols (e.g., file://, gopher://) using tools like tcpdump or netstat: sudo netstat -tunp | grep curl'}, {'type': 'list_item', 'content': 'Checking for internal file access attempts via SSRF by looking for requests with file:// URLs in the url parameter.'}] [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying the available patch identified by commit f76e7123fe093b8675f88ec8f71725b0dd186310 which modifies the handling of the url parameter in /api/System.php to prevent unsafe dynamic URL input.
Additional recommended actions are:
- Implement strict allowlisting of permitted domains or IP addresses for outbound requests initiated by the application, rejecting all others.
- Disable dangerous URL schemes such as file://, gopher://, dict://, and ftp:// if they are not required by the application.
- Enforce network-level controls to block outbound requests to internal IP ranges (e.g., 127.0.0.0/8, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, 169.254.169.254/32).
- Ensure the application does not return raw SSRF responses to users; instead, provide sanitized or generic error messages.
- Conduct regular security audits to identify and remediate vulnerabilities promptly.