# CVE-2023-4109: Ninja Forms < 3.6.26 - Admin+ Stored HTML Injection

> An attacker with admin privileges can inject malicious HTML into Ninja Forms, potentially leading to script execution or account takeover.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Aug 2023
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-hhhv-r93p-348f

## What is CVE-2023-4109?

CVE-2023-4109 is a medium-severity cross-site scripting vulnerability in Unknown Ninja Forms Contact Form, published on 30 Aug 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The Ninja Forms WordPress Ninja Forms Contact Form WordPress plugin before 3.6.26 was affected by a HTML Injection security vulnerability.

## Which versions are affected by CVE-2023-4109?

It affects 1 product.


Products: Ninjaforms Ninja Forms Contact Form.

## How do I fix CVE-2023-4109?

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

## Is CVE-2023-4109 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-4109 and fix it if it is affected.

What it is: CVE-2023-4109 is a medium-severity cross-site scripting vulnerability in Unknown Ninja Forms Contact Form, published on 30 Aug 2023. An attacker needs administrator access to exploit it, 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-2023-4109 exists.

Affected product: Unknown Ninja Forms Contact Form. 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-2023-4109/ (Markdown: https://insights.sbomify.com/CVE-2023-4109/index.md)
```

## Sources

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

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