Sansec has published details of a critical flaw in the Rootways Authorize.net CIM payment extension for Magento 2. Sansec's advisory from 17 November 2026 says an attacker already used it on 15 November to take over a Magento 2.4.8 store and plant a card skimmer. The flaw is tracked as CVE-2026-130583 (CVSS 9.2) and is fixed in version 4.1.5. If your store runs this extension, this is a job for today, not after Black Friday.
What is affected
The vulnerable module is the Rootways Authorize.net CIM extension (Composer package rootways/module-authorizecim, module Rootways_Authorizecim). According to Sansec, all versions before 4.1.5 are vulnerable, including 4.1.4 from 29 October, whose earlier Apple Pay fix did not close this hole. Rootways released 4.1.5 on 17 November, one day after Sansec reported the issue, and its advisory tells customers to update even if Apple Pay is turned off.
You can check the installed version with:
- composer show rootways/module-authorizecim
- or, for app/code installs: grep '"version"' app/code/Rootways/Authorizecim/composer.json
How the attack works
Apple Pay on the web needs a merchant validation step: the store server asks Apple for a session. Sansec found that the extension's Apple Pay controller takes the Apple URL from a request parameter and fetches it with curl without checking the host or the protocol, then returns the result to the visitor. No login is needed. That is a server-side request forgery with a full read primitive.
In practice, Sansec says, an anonymous visitor could:
- read files the PHP user can read, including app/etc/env.php with the database password and the Magento encryption key;
- send raw requests to services that only listen locally, such as Redis, Memcached or a database manager;
- query the hosting provider's cloud metadata service.
What happened in the breach Sansec investigated
In the case Sansec describes, the attacker sent 8,272 requests to the Apple Pay endpoint from 19 IP addresses. They read env.php first, then found a database manager (Adminer) listening locally on the server, logged in with the stolen database password, created their own admin account, got code execution and injected a WebSocket skimmer into every page. Sansec says the whole chain took about 14 hours. The same attacker had probed the store the evening before for older flaws such as PolyShell, SessionReaper, StyleSmuggler and BlockStrap.
What to do now
Sansec's recommended steps, in short:
- Upgrade Rootways Authorize.net CIM to 4.1.5 or later. If you cannot upgrade right away, apply the two-file patch Rootways offers in its advisory. If you bought it on the Adobe Commerce Marketplace and 4.1.5 is not listed yet, ask Rootways for it.
- Until you have upgraded, disable Apple Pay in the extension (payment/rootways_authorizecim_option_applepay/active = 0) and flush the cache.
- If Apple Pay was enabled, assume compromise: rotate the database password and the crypt key in env.php, review admin users for unknown accounts, and check the design/head/includes configuration for injected scripts.
- Scan the store for web shells and skimmers, and check for the indicators of compromise listed in the advisory.
- Put a password on Redis and restrict Adminer or other database tools to trusted IP addresses.
The wider lesson for Magento stores
This was not a Magento core bug. Your store can be fully patched against Adobe's latest bulletin and still be open through one third-party module. Before peak season it is worth listing every extension that exposes a public, unauthenticated endpoint (payments, search, chat, feeds, webhooks) and asking two questions: is it on the latest version, and does it need to be reachable at all?
The same thinking applies to any storefront add-on, including AI chat widgets. When we built Claspwell's Hyvä widget, we kept secrets out of the browser: the widget uses a public store key, origin checks, captcha and a JWT session, and the backend is isolated per store with rate limits. It is not a payment module and does not handle card data. You can read more on our security page.
If you run a Magento 2 or Hyvä store and want a second pair of eyes on which extensions face the public internet before Black Friday, get in touch.