# CVE-2022-27226: Cross-site request forgery in n/a

> A CSRF vulnerability in iRZ Mobile Routers allows attackers to create malicious crontab entries, leading to remote code execution and filesystem access.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 19 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-52c6-hmcv-vmjj

## What is CVE-2022-27226?

CVE-2022-27226 is a high-severity vulnerability in n/a, published on 19 Mar 2022. 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

A CSRF issue in /api/crontab on iRZ Mobile Routers through 2022-03-16 allows a threat actor to create a crontab entry in the router administration panel. The cronjob will consequently execute the entry on the threat actor's defined interval, leading to remote code execution, allowing the threat actor to gain filesystem access. In addition, if the router's default credentials aren't rotated or a threat actor discovers valid credentials, remote code execution can be achieved without user interaction.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 5 products.


Products: Irz Rl01 Firmware, Irz Rl21 Firmware, Irz Ru21 Firmware, Irz Ru21w Firmware, Irz Ru41 Firmware.

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

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

## Is CVE-2022-27226 being exploited?

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

Public exploit code:

- Exploit for CVE-2022-27226 (github_poc): https://github.com/SakuraSamuraii/ez-iRZ
- iRZ Mobile Router - CSRF to RCE (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-27226 is a high-severity vulnerability in n/a, published on 19 Mar 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-27226 in the wild and no public exploit code.

Affected product: n/a. 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-27226/ (Markdown: https://insights.sbomify.com/CVE-2022-27226/index.md)
```

## Sources

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

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