Scan my site freeScan free

Security notices / Rootways Authorize.net CIM Apple Pay CVE-2026-130583, rated 9.2, November 17, 2026: exploited to plant a payment skimmer, update to 4.1.5

Security notice

Use the Rootways Authorize.net CIM extension on a Magento 2 store? Sansec says a flaw in its Apple Pay feature, now tracked as CVE-2026-130583, was exploited to plant a payment skimmer. Update to 4.1.5.

Last updated: Tuesday, November 17, 2026, 5:39 PM ETStatus: Exploited, per Sansec. Update to 4.1.5 now.

Updated November 17, 2026: Sansec says this flaw is now tracked as CVE-2026-130583, with a CVSS 4.0 score of 9.2. Sansec says VulnCheck assigned the CVE on November 17. Exploitation remains Sansec's account of one incident. Previous update: Tuesday, November 17, 2026, 9:47 AM ET.

The Rootways Authorize.net CIM extension for Magento 2 has a flaw in its Apple Pay feature, in every version before 4.1.5. Sansec, writing on November 17, 2026, says the flaw lets someone without a login read store configuration and reach services on the server. Sansec says it found the flaw while investigating a hacked Magento 2.4.8 store, and that on November 15 an attacker used it to steal the store's database password and crypt key, create an administrator account, and plant a payment skimmer. That exploitation claim is Sansec's. Sansec says the flaw is now tracked as CVE-2026-130583, with a CVSS 4.0 score of 9.2. Rootways released version 4.1.5 with a fix on November 17, one day after Sansec reported the flaw. Sansec says Rootways also published a security advisory and offers a patch of the two changed files for merchants who cannot upgrade the whole extension right away. If you use this extension, update to 4.1.5 or later today. Until you have upgraded, disable Apple Pay in the extension. Sansec says Rootways still wants customers to update even when Apple Pay is turned off. If Apple Pay was enabled, assume the store is compromised. With the help of whoever runs the site, rotate the database password and the Magento crypt key. (Sansec, Nov 17)

What happened

Who should worry

Any Magento 2 store running the Rootways Authorize.net CIM extension in a version before 4.1.5. If you do not use this extension, this notice does not apply to you.

What to do now

  1. Update the Rootways Authorize.net CIM extension to 4.1.5 or later today. Back up the store first, then confirm the installed version after the update. Sansec says that if you cannot upgrade the whole extension right away, Rootways offers a patch that replaces only the two changed files, and that if you bought the extension on the Adobe Commerce Marketplace and 4.1.5 is not listed there yet, you should ask Rootways for it. (Sansec, Nov 17)
  2. Until you have upgraded, disable Apple Pay in the extension. Sansec says Rootways still wants customers to update even when Apple Pay is turned off. (Sansec, Nov 17)
  3. If Apple Pay was enabled, assume the store is compromised. With the help of whoever runs the site, rotate the database password and the Magento crypt key. Review administrator accounts for anything you do not recognize, and look for signs of a payment skimmer. Updating closes the flaw; it does not undo access an attacker may already have gained. (Sansec, Nov 17)
  4. If you find signs of a break-in, change passwords, tell affected users, and ask your developer or host to investigate.

What to send your developer, agency or host

Please check whether our Magento 2 store runs the Rootways Authorize.net CIM extension (Composer package rootways/module-authorizecim). Sansec reported a flaw in the Apple Pay feature in versions before 4.1.5. Sansec says it was exploited on November 15, 2026 to steal store configuration, create an administrator account and plant a payment skimmer. Rootways released version 4.1.5 with a fix on November 17. Sansec says the flaw is now tracked as CVE-2026-130583, with a CVSS 4.0 score of 9.2. Please update us to 4.1.5 or later today. Until the update is in place, disable Apple Pay in the extension. If Apple Pay was enabled, assume compromise: rotate the database password and the Magento crypt key, review administrator accounts, and look for signs of a payment skimmer. Then confirm the version you left us on. Source: Sansec, November 17, 2026.

Common questions

Does this mean my site was hacked?

No. A vulnerable version is a reason to update and review the store, not proof of a break-in. Sansec says this flaw has been exploited, so do not wait. If Apple Pay was enabled on a vulnerable version, assume compromise and rotate the database password and the Magento crypt key even if you have not found signs of a break-in.

Can EverThread tell me if I am affected?

No. EverThread does not test for this. We check your home page from the outside, the way a browser sees it. We cannot see which Magento extensions your store runs or which versions they are on. A scan without a warning about this extension does not mean your store is safe.

Which version should I install?

4.1.5 is the first version that fixes this flaw. Install 4.1.5 or later.

Is there a CVE?

Yes. Sansec says this flaw is now tracked as CVE-2026-130583, with a CVSS 4.0 score of 9.2, and that VulnCheck assigned the CVE on November 17, 2026.

Does this affect every Magento store?

No. The flaw is in the Rootways Authorize.net CIM extension, not in Magento or in Authorize.net itself. If you do not run this extension, this notice does not apply to you.

Where can I follow official updates?

Follow Sansec's research and any advisory from Rootways. All current notices are on our notices page.

Security alerts by email

Hear about the next one first.

When a flaw puts websites at risk, we send one email: what happened, who it affects and what to do. It's free, whether or not you use EverThread.

We email you a link to confirm first, and every alert has a one-click unsubscribe. Alerts can include a short note about EverThread. Already a customer? Use your account email and your alerts include a link to your dashboard. Privacy

Sources

While you are here

Check your site's other basics free. We look at your home page the way a browser does. This scan cannot see which Magento extensions your store runs or which versions they are on. No account.

Or sign up free and we check it every day and email you when something changes.