Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-49262 low CVSS 3.0

Vulnerability in aimeos/pagible (CVE-2026-49262)

Summary

Vulnerability in aimeos/pagible (CVE-2026-49262). Risk of unauthorized operations or information disclosure. Exploitable via cmsproxy. Mitigation: upgrade to 0.10.4 or later.

Original description

The description as published by the source.

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.

  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…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-49262 has been found in aimeos/pagible.
Attackers can target a specific entry point like cmsproxy over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.0/10.
What to do: upgrade aimeos/pagible to 0.10.4 or later.
If unsure, ask your IT team or search "aimeos/pagible CVE-2026-49262" on the vendor's site.

CVE-2026-49262 (aimeos/pagible) — CWE-367 / CVSS v3 3.0
Attack vector: remote (network-reachable)
Attack surface: cmsproxy / isValidUrl / rebound.test.com
Patched: 0.10.4 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-367) exists in aimeos/pagible. Attackers reach the vulnerable code path via cmsproxy.

📍 Affected scope

Check the vendor advisory for the affected versions of aimeos/pagible. Attack surface: cmsproxy / isValidUrl / rebound.test.com.

🔥 Severity

Severity: Low (CVSS 3.0/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.10.4.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'aimeos/pagible' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'aimeos/pagible' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で aimeos/pagible を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade aimeos/pagible to 0.10.4

    ステージング環境で 0.10.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

composer aimeos/pagible
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.10.4"}]}]
Packagist aimeos/pagible
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.10.4"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details