CVE-2026-49262

CVE-2026-49262 is a low-severity server-side request forgery (SSRF) vulnerability in aimeos/pagible (composer), affecting versions < 0.10.4. It is fixed in 0.10.4.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Aimeos Pagible CMS vulnerable to Server Side Request Forgery (SSRF) via DNS rebinding in admin proxy

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.

  1. During the validation "Check", the DNS server returns a safe, public IP.
  2. During the Guzzle "Use", the DNS server returns an internal/private IP.

POC

  1. Attacker registers `rebound.test.com with a custom nameserver.
  2. Attacker generates a valid proxy token (assuming basic authenticated access).
  3. Attacker requests /cmsproxy?url=http://rebound.test.com.
  4. isValidUrl checks rebound.test.com. DNS returns 8.8.8.8. Validation passes.
  5. Guzzle requests http://rebound.test.com. DNS returns 169.254.169.254.
  6. The CMS fetches AWS Instance Metadata and returns it to the attacker.

Impact

Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.

CVE-2026-49262 has a CVSS score of 3.0 (Low). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.10.4); upgrading removes the vulnerable code path.

Affected versions

aimeos/pagible (< 0.10.4)

Security releases

aimeos/pagible → 0.10.4 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade aimeos/pagible to 0.10.4 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is CVE-2026-49262? CVE-2026-49262 is a low-severity server-side request forgery (SSRF) vulnerability in aimeos/pagible (composer), affecting versions < 0.10.4. It is fixed in 0.10.4. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
  2. How severe is CVE-2026-49262? CVE-2026-49262 has a CVSS score of 3.0 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of aimeos/pagible are affected by CVE-2026-49262? aimeos/pagible (composer) versions < 0.10.4 is affected.
  4. Is there a fix for CVE-2026-49262? Yes. CVE-2026-49262 is fixed in 0.10.4. Upgrade to this version or later.
  5. Is CVE-2026-49262 exploitable, and should I be worried? Whether CVE-2026-49262 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2026-49262 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2026-49262? Upgrade aimeos/pagible to 0.10.4 or later.

Stop the waste.
Protect your environment with Kodem.

Get a personalized demo
Get a personalized demo