VulnerabilityPublished 24 Mar 2026

CVE-2026-4623: DefaultFuction Jeson-Customer-Relationship-Management-System · Server-Side Request Forgery

Affects DefaultFuction Jeson-Customer-Relationship-Management-SystemSource CVE Database V5

Compare

Public exploit available · CVSS 6.9 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
DefaultFuctionJeson-Customer-Relationship-Management-System	Affected =n/a	Fixed in–

AI-suggested

To mitigate CVE-2026-4623, organizations should immediately apply the vendor-provided patch identified by commit hashes f76e7123fe093b8675f88ec8f71725b0dd186310 and 98bd4eb07fa19d4f2c5228de6395580013c97476. Beyond patching, implement strict input validation and sanitization on all URL parameters to ensure only allowed and safe destinations can be requested. Employ allowlisting of outbound requests from the CRM server to restrict connections to trusted endpoints only. Network segmentation should isolate the CRM server from sensitive internal services to limit SSRF impact. Monitor outbound traffic logs for unusual or unexpected requests originating from the CRM server. Use web application firewalls (WAFs) with SSRF detection capabilities to block suspicious requests. Conduct regular security assessments and penetration testing focused on SSRF and related vulnerabilities. Finally, maintain up-to-date inventory and awareness of all CRM system components and their update status to ensure timely patching in continuous delivery environments.

Description

A security vulnerability has been detected in DefaultFuction Jeson-Customer-Relationship-Management-System up to 1b4679c4d06b90d31dd521c2b000bfdec5a36e00. This affects an unknown function of the file /api/System.php of the component API Module. The manipulation of the argument url leads to server-side request forgery. The attack can be initiated remotely. The exploit has been disclosed publicly and may be used. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. The identifier of the patch is f76e7123fe093b8675f88ec8f71725b0dd186310/98bd4eb07fa19d4f2c5228de6395580013c97476. It is suggested to install a patch to address this issue.

Impact

The SSRF vulnerability in Jeson-CRM can have significant impacts on affected organizations. Attackers can exploit it to make the server send unauthorized requests to internal or external systems, potentially accessing sensitive internal services, metadata endpoints, or cloud provider APIs. This can lead to unauthorized data disclosure, internal network reconnaissance, or pivoting to further attacks such as lateral movement or privilege escalation. The integrity of internal systems may be compromised if attackers can interact with internal APIs or services. Availability could also be affected if attackers use SSRF to trigger denial-of-service conditions on internal resources. Since the vulnerability requires no authentication or user interaction, it can be exploited at scale by remote attackers. Organizations relying on Jeson-CRM for customer relationship management risk exposure of confidential customer data and disruption of business processes. The medium CVSS score reflects moderate but non-trivial risk, especially in environments with sensitive internal infrastructure behind the CRM server.

Summary

CVE-2026-4623 identifies a server-side request forgery (SSRF) vulnerability in the DefaultFuction Jeson-Customer-Relationship-Management-System, affecting an unspecified function within the /api/System.php file of the API module. The vulnerability is triggered by manipulation of the 'url' argument, which the system uses without adequate validation or sanitization, allowing attackers to make the server perform arbitrary HTTP requests. SSRF vulnerabilities can be leveraged to access internal services, bypass firewalls, or interact with sensitive backend infrastructure that is otherwise inaccessible externally. The vulnerability can be exploited remotely without any authentication or user interaction, increasing its risk profile. The product uses continuous delivery with rolling releases, complicating precise version identification, but patches have been committed under specific identifiers. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P) reflects network attack vector, low attack complexity, no privileges or user interaction required, and partial impacts on confidentiality, integrity, and availability. No known exploits are currently active in the wild, but public disclosure raises the risk of future exploitation. The vulnerability affects organizations using this CRM system, potentially exposing internal network resources and sensitive data to attackers.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Mar 2026, 16:03 UTC

Technical details

References

Community reviews

Related threats