Skip to main content
VulnerabilityPublished Updated

CVE-2022-38931: baijiacmsV4 · Server-Side Request Forgery (SSRF)

Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.3% chance of exploitation in 30 days – higher than 70% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Sep 2022

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
n/a n/aAffected
  • =4.1.4
Fixed in–

AI-suggested

Specific mitigation steps include: 1) Immediate identification of all baijiacmsV4 version 4.1.4 deployments within the organization. 2) Applying any available patches or updates from the vendor; if none are available, consider upgrading to a later, unaffected version or applying vendor-recommended workarounds. 3) Implement strict input validation and sanitization on the 'url' parameter to restrict requests to trusted domains or IP ranges, effectively preventing arbitrary URL injection. 4) Employ network segmentation and firewall rules to limit the CMS server's ability to initiate outbound requests to internal or sensitive network segments. 5) Monitor outbound traffic from the CMS server for unusual or unauthorized requests that could indicate exploitation attempts. 6) Conduct regular security audits and penetration testing focusing on SSRF vectors. 7) Educate development and operations teams about SSRF risks and secure coding practices to prevent similar vulnerabilities in the future.

Description

A Server-Side Request Forgery (SSRF) in fetch_net_file_upload function of baijiacmsV4 v4.1.4 allows remote attackers to force the application to make arbitrary requests via injection of arbitrary URLs into the url parameter.

References

Community reviews

Loading reviews…