Unauthenticated SSRF via unchecked QR code URL
Published Jun 3, 2026 · Updated Jun 3, 2026
SSRF in CRMEB Java 1.4 allows remote attackers to send arbitrary HTTP requests through the unauthenticated base64 QR code endpoint. POST /api/front/qrcode/base64 passes its url parameter through getBuffer directly to RestTemplate.getForEntity without validation. No credentials are required because the route is excluded from the front-token interceptor; responses expose the reachability of internal services.
Summary
What happened
SSRF in CRMEB Java 1.4 allows remote attackers to send arbitrary HTTP requests through the unauthenticated base64 QR code endpoint. POST /api/front/qrcode/base64 passes its url parameter through getBuffer directly to RestTemplate.getForEntity without validation. No credentials are required because the route is excluded from the front-token interceptor; responses expose the reachability of internal services.
The record
- CVE
- CVE-2026-10771
- Published
- Jun 3, 2026
- Updated
- Jun 3, 2026
- Vendor
- CRMEB
- Product
- CRMEB Java
- Classifications
- CWE-918, T1046, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 3, 2026CVE publishedPublication date reported by the CVE source.
- Jun 3, 2026Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.4
What conditions does exploitation require?
What is affected?
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
- GitHub Issue 35 SSRF proof of conceptproof of concept · demonstrated
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