Skip to main content
VulnerabilityPublished Updated

CVE-2022-40357: Server-Side Request Forgery (SSRF)

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.5% chance of exploitation in 30 days – higher than 74% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/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
GitHubzblogcn/zblogphppkg:github/zblogcn/zblogphpOther threatsAffected
  • <=1.7.2
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediate mitigation should include restricting access to the vulnerable endpoint (zb_users/plugin/UEditor/php/action_crawler.php) via network controls such as web application firewalls (WAFs) or reverse proxies to block unauthorized or suspicious requests targeting the 'source' parameter.
  2. Implement strict input validation and sanitization on the 'source' parameter to ensure only allowed URLs or domains can be requested, ideally limiting requests to trusted internal or external endpoints.
  3. If possible, disable or remove the vulnerable UEditor plugin or the crawler functionality until an official patch is released.
  4. Monitor application logs for unusual outbound HTTP requests initiated by the server, which could indicate exploitation attempts.
  5. Employ network segmentation and egress filtering to limit the server's ability to make arbitrary outbound requests, reducing the potential impact of SSRF exploitation.
  6. Stay updated with Z-BlogPHP vendor communications for official patches or security advisories and apply them promptly once available.
  7. Conduct internal security assessments and penetration testing to identify if the vulnerability is exploitable within the organization's environment and to validate the effectiveness of mitigations.

Description

A security issue was discovered in Z-BlogPHP <= 1.7.2. A Server-Side Request Forgery (SSRF) vulnerability in the zb_users/plugin/UEditor/php/action_crawler.php file allows remote attackers to force the application to make arbitrary requests via injection of arbitrary URLs into the source parameter.

References

Community reviews

Loading reviews…