aimeos/pagible
Affected
- introduced
0, fixed0.10.4(ecosystem)
Fixed versions
0.10.4
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-49262
Aimeos Pagible CMS vulnerable to Server Side Request Forgery (SSRF) via DNS rebinding in admin proxy
Summary
The administrative proxy route (cmsproxy) in Aimeos Pagible CMS is vulnerable to a Server-Side Request Forgery (SSRF) attack via DNS Rebinding. A Time-of-Check to Time-of-Use (TOCTOU) race condition exists between the URL validation phase and the actual HTTP request phase, allowing attackers to access internal network resources and cloud metadata endpoints.
Details
Before executing an HTTP request to fetch external content, the AdminController::proxy controller validates the target URL using \Aimeos\Cms\Utils::isValidUrl($url). This function performs a DNS query to verify that the hostname does not resolve to private or reserved IP ranges (e.g., 127.0.0.1, 10.0.0.0/8, 169.254.169.254).
If the validation passes, the application proceeds to the "Use" phase, invoking Guzzle/cURL to send the request. However, Guzzle performs a *second* DNS lookup to establish the socket connection.
An attacker can exploit this by setting up a malicious DNS server for a domain they control and configuring it with a TTL of 0.
### POC
/cmsproxy?url=http://rebound.test.com.isValidUrl checks rebound.test.com. DNS returns 8.8.8.8. Validation passes.http://rebound.test.com. DNS returns 169.254.169.254.Low Basis: The source's own band: LOW
0, fixed 0.10.4 (ecosystem)0.10.4
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0