SSRF via unrestricted UEditor source URLs
Published Sep 20, 2022 · Updated May 28, 2025
SSRF in Z-BlogPHP 1.7.2 and earlier allows remote attackers to make arbitrary server-side requests through the UEditor crawler. The catchimage route passes each unrestricted source URL to saveRemote, which checks only for an http prefix before calling get_headers. This permits intranet service probing; the public proof uses an administrator session cookie, although the record classifies access as unauthenticated.
Summary
What happened
SSRF in Z-BlogPHP 1.7.2 and earlier allows remote attackers to make arbitrary server-side requests through the UEditor crawler. The catchimage route passes each unrestricted source URL to saveRemote, which checks only for an http prefix before calling get_headers. This permits intranet service probing; the public proof uses an administrator session cookie, although the record classifies access as unauthenticated.
The record
- CVE
- CVE-2022-40357
- Published
- Sep 20, 2022
- Updated
- May 28, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 20, 2022CVE publishedPublication date reported by the CVE source.
- May 28, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream issue proof-of-concept HTTP requestproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo