On November 17, 2026, VulnCheck (acting as CNA) published CVE-2026-130583 in NVD: an unauthenticated server-side request forgery in the Rootways Authorize.net CIM Pro payment extension for Magento 2. This isn't a Magento core bug but a third-party module running on live stores. And what it lets an attacker read is exactly what a store guards most closely: app/etc/env.php, with the database credentials and the encryption key.
Rootways has shipped a fix (version 4.1.5), and the flaw was documented by e-commerce security firm Sansec.
The vulnerability
| CVE | CVE-2026-130583 |
| Product | Rootways Authorize.net CIM Pro for Magento 2 |
| Affected versions | before 4.1.5 |
| Type | Server-Side Request Forgery (CWE-918) |
| CVSS 3.1 | 9.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N, VulnCheck) |
| CVSS 4.0 | 9.2 (VulnCheck) |
| Authentication | None |
| NVD status | Received (not analyzed) |
| CISA KEV | No, at the time of writing |
How it works
To offer Apple Pay, a store has to validate its merchant session with Apple: the browser gets a validation URL, and the store's server calls it. The extension exposes an Apple Pay merchant validation controller for this, which takes the URL in the validationUrl parameter.
According to the NVD description, that controller restricts neither the target nor the scheme. An unauthenticated attacker can supply a file://, gopher:// or dict:// URL and get the server to do the work:
file://: read local files, includingapp/etc/env.php, which holds the database credentials and Magento's encryption key;gopher://anddict://: talk to internal services (Redis, memcached, databases, admin interfaces that aren't exposed);- HTTP to cloud metadata: reach the hosting provider's metadata endpoints, which can hand out temporary credentials.
That's what the S:C in the vector reflects: the impact goes beyond the extension to whatever systems the server can reach.
Why it matters
Magento's encryption key protects data stored in the database (payment configuration, tokens, some integration secrets). With that key and the database credentials, an attacker who reaches the database, directly or through another internal service, can read and modify the store in depth. That's our inference from what env.php contains, not a scenario the CVE describes.
It's also the kind of bug that card-skimming groups go after: a payment extension, exploitable without an account, on production stores. The NVD entry doesn't document any exploitation so far.
Magento stores are a regular target: in September, a template injection in Adobe Commerce core was added to the CISA KEV catalog.
Affected versions
| Product | Affected | Fixed |
|---|---|---|
| Rootways Authorize.net CIM Pro (Magento 2) | before 4.1.5 | 4.1.5 |
NVD has no CPE configuration for this extension yet. The fixed version comes from VulnCheck's description and the Rootways security post it references.
Detection
- Inventory: check whether the Rootways Authorize.net CIM Pro module is installed (
composer show, or the module list inapp/etc/config.php) and which version. - Web logs: requests to the extension's Apple Pay validation controller where
validationUrlcontainsfile://,gopher://,dict://, a private address or the cloud metadata address. A legitimate validation URL points to an Apple domain over HTTPS. - Outbound traffic: connections from the web server to internal services or cloud metadata that don't match any known use.
- Database and admin: recently created admin accounts, changes to payment configuration, unexpected scripts in CMS blocks or HTML configuration fields.
Mitigation
1. Update to 4.1.5
That's the fix. Then flush the cache and recompile (setup:di:compile) if your deployment mode requires it.
2. If you don't use Apple Pay
Turn off the extension's Apple Pay option until you can update: the vulnerable controller exists to serve that feature.
3. Limit what the server can reach
Filter outbound traffic from the web server, and enforce IMDSv2 (or your provider's equivalent) for cloud metadata access.
4. If the store may have been exposed
Assume env.php was read: change the database credentials, rotate Magento's encryption key (the procedure re-encrypts stored data) and renew integration secrets (payment APIs, carriers, ERP). Review admin accounts and any injectable content.
Why continuous monitoring matters for your store's extensions
A Magento store is the Adobe core plus dozens of third-party extensions, each with its own patch cycle. This one has no CPE in NVD, so monitoring limited to Magento core wouldn't have caught it.
With cveo.tech, add your extensions to your inventory with their version and get an alert as soon as a CVE affects them, even before NIST analysis.