# CVE-2026-130583: Rootways Authorize.net CIM Pro for Magento 2 before 4.1.5 SSRF via Apple Pay Validation


- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-qm2w-gc8x-h327

## What is CVE-2026-130583?

CVE-2026-130583 is a critical vulnerability in Rootways Authorize.net CIM Pro extension for Magento 2, published on 17 Nov 2026. 

### Official description

Rootways Authorize.net CIM Pro extension for Magento 2 before 4.1.5 contains an unauthenticated server-side request forgery vulnerability in the Apple Pay merchant validation controller. Attackers can supply file://, gopher://, or dict:// URLs in the validationUrl parameter to read app/etc/env.php credentials and encryption keys or reach internal services and cloud metadata endpoints.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-130583?

1 open source package ship an affected version, including rootways/module-authorizecim.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `rootways/module-authorizecim` | Packagist | `pkg:composer/rootways/module-authorizecim` | All versions | 4.1.5 |

## How do I fix CVE-2026-130583?

Upgrade rootways/module-authorizecim to 4.1.5 or later.

## Is CVE-2026-130583 being exploited?

There is no known exploitation of CVE-2026-130583 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-130583 and fix it if it is affected.

What it is: CVE-2026-130583 is a critical vulnerability in Rootways Authorize.net CIM Pro extension for Magento 2, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130583 in the wild and no public exploit code.

Affected packages and fixed versions:
- rootways/module-authorizecim (Packagist): affected all versions; fixed in 4.1.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-130583/ (Markdown: https://insights.sbomify.com/CVE-2026-130583/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-130583
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-130583
- OSV: https://osv.dev/vulnerability/CVE-2026-130583

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-130583/
Summaries are generated and may contain mistakes; the official description above is the record.
