# CVE-2022-4117: IWS - Geo Form Fields <= 1.0 - Unauthenticated SQLi

> Unauthenticated attackers can perform SQL injection via an AJAX action in the IWS Geo Form Fields WordPress plugin, potentially accessing or modifying database content.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 26 Dec 2022
- **Updated:** 14 Apr 2025
- **Also known as:** GHSA-9h74-mx6m-3v5r

## What is CVE-2022-4117?

CVE-2022-4117 is a critical SQL injection vulnerability in Unknown IWS, published on 26 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The IWS WordPress plugin through 1.0 does not properly escape a parameter before using it in a SQL statement via an AJAX action available to unauthenticated users, leading to an unauthenticated SQL injection.

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

It affects 1 product.


Products: Iws-Geo-Form-Fields Project Iws-Geo-Form-Fields.

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

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

## Is CVE-2022-4117 being exploited?

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

Public exploit code:

- WordPress IWS Geo Form Fields <=1.0 - SQL Injection (nuclei): http/cves/2022/CVE-2022-4117.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2022-4117 is a critical SQL injection vulnerability in Unknown IWS, published on 26 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4117 exists.

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

## Sources

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

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