# CVE-2025-24966: HTML Injection in reNgine

> Attackers can inject HTML into reNgine target fields to execute malicious scripts, potentially stealing data or compromising user sessions.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Feb 2025
- **Updated:** 4 Feb 2025
- **Also known as:** GHSA-4phc-m2wm-p8x6

## What is CVE-2025-24966?

CVE-2025-24966 is a medium-severity cross-site scripting vulnerability in yogeshojha rengine, published on 4 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

reNgine is an automated reconnaissance framework for web applications. HTML Injection occurs when an application improperly validates or sanitizes user inputs, allowing attackers to inject arbitrary HTML code. In this scenario, the vulnerability exists in the "Add Target" functionality of the application, where the Target Organization and Target Description fields accept HTML payloads. The injected HTML is rendered and executed in the target area, potentially leading to malicious actions. Exploitation of HTML Injection can compromise the application's integrity and user trust. Attackers can execute unauthorized actions, steal sensitive information, or trick users into performing harmful actions. The organization's reputation, customer trust, and regulatory compliance could be negatively affected. This issue affects all versions up to and including 2.2.0. Users are advised to monitor the project for future releases which address this issue. There are no known workarounds.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-24966?

It affects 1 product.


Products: Yogeshojha Rengine.

## How do I fix CVE-2025-24966?

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

## Is CVE-2025-24966 being exploited?

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

## Other vulnerabilities in yogeshojha rengine

- [CVE-2022-36566](https://insights.sbomify.com/CVE-2022-36566/): Command injection in n/a (critical 9.8)
- [CVE-2022-28995](https://insights.sbomify.com/CVE-2022-28995/): Code injection in n/a (critical 9.8)
- [CVE-2021-38606](https://insights.sbomify.com/CVE-2021-38606/): Information disclosure in n/a (critical 9.8)
- [CVE-2025-24968](https://insights.sbomify.com/CVE-2025-24968/): Business Logic And Unrestricted Project Deletion Lead To Take Over the System in reNgine (high 8.8)
- [CVE-2023-50094](https://insights.sbomify.com/CVE-2023-50094/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-24966 and fix it if it is affected.

What it is: CVE-2025-24966 is a medium-severity cross-site scripting vulnerability in yogeshojha rengine, published on 4 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-24966 exists.

Affected product: yogeshojha rengine. 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-2025-24966/ (Markdown: https://insights.sbomify.com/CVE-2025-24966/index.md)
```

## Sources

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

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