# CVE-2026-2222: code-projects Online Reviewer System btn_functions.php cross site scripting

> Remote attackers can execute arbitrary scripts via the firstname parameter in the admin user management interface, potentially compromising user sessions.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **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:** 9 Feb 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-h4hx-hmx9-44gm

## What is CVE-2026-2222?

CVE-2026-2222 is a medium-severity cross-site scripting vulnerability in code-projects Online Reviewer System, published on 9 Feb 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

A weakness has been identified in code-projects Online Reviewer System 1.0. Affected by this vulnerability is an unknown functionality of the file /system/system/admins/manage/users/btn_functions.php. Executing a manipulation of the argument firstname can lead to cross site scripting. The attack may be performed from remote. The exploit has been made available to the public and could be used for attacks.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-2222?

It affects 1 product.


Products: Fabian Online Reviewer System.

## How do I fix CVE-2026-2222?

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

## Is CVE-2026-2222 being exploited?

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

Public exploit code:

- https://github.com/George0Papasotiriou/CVE-2026-2222-MQTT-Broker-CONNECT-Packet-Heap-Overflow (github_poc): https://github.com/George0Papasotiriou/CVE-2026-2222-MQTT-Broker-CONNECT-Packet-Heap-Overflow

## Other vulnerabilities in code-projects Online Reviewer System

- [CVE-2026-2912](https://insights.sbomify.com/CVE-2026-2912/): code-projects Online Reviewer System studentresult-view.php sql injection (medium 6.9)
- [CVE-2026-2196](https://insights.sbomify.com/CVE-2026-2196/): code-projects Online Reviewer System exam-update.php sql injection (medium 6.9)
- [CVE-2026-2197](https://insights.sbomify.com/CVE-2026-2197/): code-projects Online Reviewer System exam-delete.php sql injection (medium 6.9)
- [CVE-2026-2198](https://insights.sbomify.com/CVE-2026-2198/): code-projects Online Reviewer System loaddata.php sql injection (medium 6.9)
- [CVE-2026-2199](https://insights.sbomify.com/CVE-2026-2199/): code-projects Online Reviewer System user-delete.php sql injection (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-2222 and fix it if it is affected.

What it is: CVE-2026-2222 is a medium-severity cross-site scripting vulnerability in code-projects Online Reviewer System, published on 9 Feb 2026. 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-2026-2222 exists.

Affected product: code-projects Online Reviewer System. 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-2026-2222/ (Markdown: https://insights.sbomify.com/CVE-2026-2222/index.md)
```

## Sources

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

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