On this page (7 sections)
A critical vulnerability, tracked as CVE-2026-130583, affects the Rootways Authorize.net CIM Pro extension for Magento 2 in versions before 4.1.5. According to the GitHub Advisory Database entry, the Apple Pay merchant validation controller contains an unauthenticated server-side request forgery (SSRF) flaw.
If you run a Magento 2 store that uses this extension, treat this as urgent. The advisory says the flaw can be used to read the credentials and encryption keys stored in Magento's app/etc/env.php file, or to reach internal services and cloud metadata endpoints. Only one independent publisher covers this story so far, so some details below are limited to what the advisory states.
What happened
The vulnerability was published on November 17, 2026. The advisory describes a flaw in the controller that handles Apple Pay merchant validation. That controller accepts a parameter named validationUrl, and the advisory says an unauthenticated attacker can supply file://, gopher:// or dict:// URLs in it.
The advisory lists the following CVSS v4 metrics: network attack vector, low attack complexity, no attack requirements, no privileges required and no user interaction. Confidentiality impact is rated high and integrity impact low. Together these produce the 9.2 score.
The advisory references a Sansec research write-up, a Rootways security update post for version 4.1.5, and a VulnCheck advisory. The research available for this article did not include the text of those pages, so details such as exploitation in the wild or exact upgrade notes should be confirmed there.
How this type of flaw works
Server-side request forgery means an attacker persuades your server to make a request on their behalf. Normally an Apple Pay validation step would contact an Apple endpoint. If the server fetches whatever address the visitor supplies without checking it, the visitor controls where the server connects.
That matters because the server sits inside your network and can reach things the public internet cannot. The advisory names three consequences: reading local files through file:// URLs, talking to internal services, and reaching cloud metadata endpoints. Cloud metadata services can hand out temporary credentials to anything running on the instance, which is why SSRF is often a stepping stone to a wider compromise.
The file named in the advisory, app/etc/env.php, is where Magento keeps database credentials and the encryption key, among other settings. Exposure of that file is more serious than a single bug suggests, because the secrets remain useful to an attacker after the extension itself is patched.
Who is affected
- Magento 2 stores with the Rootways Authorize.net CIM Pro extension installed at a version below 4.1.5.
- Agencies and hosts that manage such stores for clients, including staging and forgotten test copies.
- Stores on cloud hosting, where metadata endpoints may be reachable from the web server.
The advisory does not say whether the vulnerable controller is reachable only when Apple Pay is enabled in the extension settings. Do not assume a store is safe because Apple Pay is switched off; confirm with Rootways or test on a staging copy.
How to check your exposure
First find out whether the extension is installed and which version you run. This Composer command, run from the Magento root directory, lists installed packages and filters for Rootways. The package name may differ depending on how the extension was installed, so a no-match result does not prove it is absent.
composer show | grep -i rootwaysIf the extension was installed manually rather than through Composer, look in app/code for a Rootways directory and check the version in the module's composer.json or in the Rootways account area.
ls app/code | grep -i rootwaysNext, review web server access logs for requests to the Apple Pay validation endpoint that carry a validationUrl value beginning with file://, gopher://, dict:// or an internal address. The exact controller path is not given in the research, so search on the parameter name instead. Any hit from an unfamiliar client should be treated as a possible compromise.
grep -i 'validationUrl' /var/log/nginx/access.log*What to do now
- Confirm whether the Rootways Authorize.net CIM Pro extension is installed and note its version.
- Update to version 4.1.5 or later, following the instructions in the Rootways security update post.
- Test the Apple Pay and card checkout flows on staging before and after the update.
- Search access logs for validationUrl requests, especially with file://, gopher:// or dict:// values.
- If you see suspicious requests, or cannot rule out exposure, rotate the database password and other secrets in app/etc/env.php, and plan for the Magento encryption key as well.
- Rotate any cloud credentials available to the server and review cloud audit logs for unusual use.
- Restrict outbound traffic from the web server so it cannot reach internal services or metadata endpoints unless needed.
- If you cannot patch immediately, consider disabling the extension or its Apple Pay feature until you can, after confirming this with Rootways.
Detection and monitoring afterwards
Patching closes the hole but does not undo any earlier access. Keep the relevant logs from before the update, since they are your only record of whether the endpoint was probed. Watch for unexpected logins to the Magento admin, new admin users, database connections from unfamiliar addresses and unusual API calls using your cloud credentials.
Because this extension sits in the payment path, also keep an eye on checkout pages for scripts you did not add. Alerts for new scripts on checkout pages help with that, and the guide to card skimming explains why stolen store credentials are often followed by skimmer injection. For general hygiene on a store, see security for online stores.
What we do not know yet
- Whether the flaw is being exploited in the wild. The research does not say.
- The exact controller path and the upgrade steps beyond version 4.1.5.
- Whether any configuration, such as Apple Pay being disabled, prevents the vulnerable code from being reached.
- How many stores have the extension installed.
Until Rootways and Sansec details are confirmed against your own setup, assume any unpatched, internet-facing store with this extension is exposed.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
