Skip to content
Rootways CIM Pro flaw CVE-2026-130583 lets attackers read Magento 2 store keys
Black Shard

Loading

    AdvisoriesCritical severity

    Rootways CIM Pro flaw CVE-2026-130583 lets attackers read Magento 2 store keys

    The flaw sits in the extension's Apple Pay merchant validation step, needs no sign-in, and also reaches internal services and cloud metadata endpoints behind the store.

    Black Shard Advisories

    2 min read

    Share

    Affects

    Rootways CIM Pro extension for

    What to do

    Update the Rootways CIM Pro extension to 4.1.5, then rotate every credential in app/etc/env.php.

    On this page
    1. How the flaw works
    2. What to do now
    3. Who is affected
    4. Detection notes
    5. Essential Eight mapping
    Advisory BS-ADV-2026-0018
    NVD published
    CVE
    CVE-2026-130583
    CVSS
    9.3 (v3.1, VulnCheck)9.2 (v4.0, VulnCheck)
    Exploitation
    None known
    Affected
    • Rootways CIM Pro extension for Magento 2
    • Versions before 4.1.5
    Fixed in
    • 4.1.5

    How the flaw works

    The extension's Apple Pay merchant validation controller takes an address in its validationUrl parameter and needs no sign-in. An attacker who supplies a file://, gopher:// or dict:// address can read app/etc/env.php, with the store's credentials and encryption keys, or reach internal services and cloud metadata endpoints.

    What to do now

    Start with the live storefront, because the validation controller answers anyone on the internet and can read app/etc/env.php.

    1. Find every Magento 2 store, staging copies included, running the Rootways CIM Pro extension
    2. Update the extension to the fixed release
    3. Rotate the database password and every other credential held in app/etc/env.php
    4. Rotate the encryption keys held in app/etc/env.php
    5. Rotate cloud credentials the web host can obtain from its metadata endpoint

    Who is affected

    Any Magento 2 store running the extension below the fixed release is exposed to anyone on the internet, because the controller asks for no authentication. A store hosted in a cloud account carries more risk, since the flaw reaches cloud metadata endpoints as well as the store's own files.

    Detection notes

    The attack arrives as an ordinary web request to the payment controller, so the web server access log and the host's outbound traffic are where to look, across every log the host still holds.

    • Requests whose validationUrl value starts with file://, gopher:// or dict://
    • Hits on the Apple Pay validation controller from visitors who never reached checkout
    • Outbound connections from the web host to internal addresses or the cloud metadata address
    • Database or admin sign-ins with the store's credentials from unfamiliar addresses

    Essential Eight mapping

    Patch applications: the Essential Eight Maturity Model sets 48 hours for internet-facing services when vulnerabilities are assessed as critical by vendors or working exploits exist. Restrict administrative privileges and multi-factor authentication on the Magento admin limit what stolen credentials reach.

    Affected by this advisory?

    Tell us what you run. We patch, contain and check for signs of compromise.