CVE-2026-49262: Aimeos/pagible Aimeos Pagible CMS Vulnerable To Vulnerability
LOWCVE-2026-49262 is a LOW (CVSS 3.0) aimeos pagible cms vulnerable to vulnerability (CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition) affecting Aimeos/pagible libraries in the Packagist ecosystem. The issue involves aimeos pagible cms vulnerable to server side request forgery (ssrf) via dns rebinding in admin proxy. Remediation is available by upgrading affected packages to version 0.10.4.
CVE-2026-49262 at a Glance
Security Impact
CVSS: 3.0
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:N/A:N).
How to Fix CVE-2026-49262
To remediate this vulnerability, upgrade all affected Aimeos/pagible dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade aimeos/pagible to 0.10.4
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for aimeos/pagible
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-49262, inspect your project dependencies for Aimeos/pagible:
inspect dependencies for aimeos/pagible
Analyze the terminal output to locate any version of Aimeos/pagible in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.10.4), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition, where the product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check. In Aimeos/pagible, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-49262 Affected Aimeos/pagible Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
aimeos/pagible
|
Packagist |
< 0.10.4
|
0.10.4
|
References
Frequently Asked Questions
What is CVE-2026-49262?
Which Aimeos/pagible versions are affected?
What version fixes CVE-2026-49262?
Is aimeos/pagible affected?
What is the CVSS score of CVE-2026-49262?
What CWE is associated with CVE-2026-49262?
How can I check Packagist dependencies for CVE-2026-49262?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-mmj8-wcvw-6789",
"modified" : "2026-06-26T21:50:10Z",
"published" : "2026-06-26T21:50:10Z",
"aliases" : [ "CVE-2026-49262" ],
"summary" : "Aimeos Pagible CMS vulnerable to Server Side Request Forgery (SSRF) via DNS rebinding in admin proxy",
"details" : "### Summary\nThe 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.\n\n### Details\nBefore 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`). \n\nIf 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. \n\nAn attacker can exploit this by setting up a malicious DNS server for a domain they control and configuring it with a TTL of 0. \n1. During the validation \"Check\", the DNS server returns a safe, public IP.\n2. During the Guzzle \"Use\", the DNS server returns an internal/private IP.\n\n ### POC\n1. Attacker registers `rebound.test.com with a custom nameserver.\n2. Attacker generates a valid proxy token (assuming basic authenticated access).\n3. Attacker requests `/cmsproxy?url=http://rebound.test.com`.\n4. `isValidUrl` checks `rebound.test.com`. DNS returns `8.8.8.8`. Validation passes.\n5. Guzzle requests `http://rebound.test.com`. DNS returns `169.254.169.254`.\n6. The CMS fetches AWS Instance Metadata and returns it to the attacker.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:N/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Packagist",
"name" : "aimeos/pagible"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.10.4"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/aimeos/pagible/security/advisories/GHSA-mmj8-wcvw-6789"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/aimeos/pagible"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-367", "CWE-918" ],
"severity" : "LOW",
"github_reviewed" : true,
"github_reviewed_at" : "2026-06-26T21:50:10Z",
"nvd_published_at" : null
}
}