An unauthenticated server-side request forgery flaw in the Apple Pay merchant validation controller of Rootways' Authorize.net CIM Pro extension for Magento 2 lets attackers read local files, according to the VulnCheck advisory, including credentials and encryption keys, and reach internal services.
What Is It
CVE-2026-130583 is a server-side request forgery (SSRF) vulnerability (CWE-918) in the Rootways Authorize.net CIM Pro extension for Magento 2. The flaw is in the Apple Pay merchant validation controller. The controller accepts a validationUrl parameter, and attackers can put URLs that use the file, gopher or dict schemes in it. No authentication is required.
VulnCheck reported the issue, and it was published to NVD on 2026-11-17. The NVD record is in "Received" status, which means NVD has not analyzed it yet.
Why It Matters
According to the record, attackers can abuse this flaw to:
- Read
app/etc/env.php, which holds Magento credentials and encryption keys - Reach internal services that are not exposed to the internet
- Query cloud metadata endpoints
VulnCheck scores it CVSS 3.1 9.3 (CRITICAL) with vector AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N: network-reachable, low complexity, no privileges or user interaction, and a changed scope. The CVSS 4.0 score is 9.2 (CRITICAL). It is a payment-processing extension on e-commerce storefronts, so exposed secrets could put the wider Magento installation and its connected systems at risk.
This CVE is not in the CISA Known Exploited Vulnerabilities catalog, and the supplied data does not confirm active exploitation.
What's Vulnerable
- Vendor: Rootways
- Product: Authorize.net CIM Pro extension for Magento 2
- Package:
pkg:composer/rootways/module-authorizecim - Affected versions: all versions before 4.1.5
The record lists no CPEs.
Patch Status
The flaw affects versions before 4.1.5, and Rootways has published a security update for v4.1.5 that covers the Apple Pay issue. Administrators should upgrade to 4.1.5 or later. The exposed file (app/etc/env.php) holds Magento credentials and encryption keys, so stores that ran an affected version should also check whether those secrets need to be replaced. There is no CISA KEV entry, so no federal required action or due date applies.