# CVE-2022-4426: Mautic Integration For WooCommerce < 1.0.3 - Arbitrary Options Update via CSRF

> Attackers can trick logged-in admins into changing arbitrary blog options via CSRF in the Mautic Integration for WooCommerce plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Jan 2023
- **Updated:** 9 Apr 2025
- **Also known as:** GHSA-c2gf-h728-j378

## What is CVE-2022-4426?

CVE-2022-4426 is a medium-severity vulnerability in Unknown Mautic Integration for WooCommerce, published on 9 Jan 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Mautic Integration for WooCommerce WordPress plugin before 1.0.3 does not have proper CSRF check when updating settings, and does not ensure that the options to be updated belong to the plugin, allowing attackers to make a logged in admin change arbitrary blog options via a CSRF attack.

## Which versions are affected by CVE-2022-4426?

It affects 1 product.


Products: Wpswings Mautic Integration for Woocommerce.

## How do I fix CVE-2022-4426?

No fix has been published for CVE-2022-4426 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-4426 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4426 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-4426 and fix it if it is affected.

What it is: CVE-2022-4426 is a medium-severity vulnerability in Unknown Mautic Integration for WooCommerce, published on 9 Jan 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4426 exists.

Affected product: Unknown Mautic Integration for WooCommerce. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2022-4426/ (Markdown: https://insights.sbomify.com/CVE-2022-4426/index.md)
```

## Sources

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

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