CVE-2026-49262 is a low-severity (CVSS 3) CWE-367 vulnerability in aimeos/pagible. A fix is available for aimeos/pagible — see the affected versions and patch details below.
Aimeos Pagible CMS vulnerable to Server Side Request Forgery (SSRF) via DNS rebinding in admin proxy
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-49262.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
aimeos/pagibleReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
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.
- During the validation "Check", the DNS server returns a safe, public IP.
- During the Guzzle "Use", the DNS server returns an internal/private IP.
POC
- Attacker registers `rebound.test.com with a custom nameserver.
- Attacker generates a valid proxy token (assuming basic authenticated access).
- Attacker requests
/cmsproxy?url=http://rebound.test.com. isValidUrlchecksrebound.test.com. DNS returns8.8.8.8. Validation passes.- Guzzle requests
http://rebound.test.com. DNS returns169.254.169.254. - The CMS fetches AWS Instance Metadata and returns it to the attacker.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | aimeos/pagible | all versions | 0.10.4composer require aimeos/pagible:^0.10.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for aimeos/pagible, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update aimeos/pagible to 0.10.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-49262 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.
Frequently Asked Questions
Is CVE-2026-49262 in your dependencies?
Find it across Packagist, including transitive dependencies.