# CVE-2025-9439: 1000projects Online Project Report Submission and Evaluation System edit_faculty.php cross site scripting

> Remote attackers can inject malicious scripts via the Name parameter in the faculty editing interface, potentially compromising user sessions.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **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:** 26 Aug 2025
- **Updated:** 26 Aug 2025
- **Also known as:** GHSA-9wjv-9mc7-hwv7

## What is CVE-2025-9439?

CVE-2025-9439 is a medium-severity cross-site scripting vulnerability in 1000projects Online Project Report Submission and Evaluation System, published on 26 Aug 2025. 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 weakness has been identified in 1000projects Online Project Report Submission and Evaluation System 1.0. Affected by this vulnerability is an unknown functionality of the file /rse/admin/edit_faculty.php?id=2. This manipulation of the argument Name causes cross site scripting. The attack is possible to be carried out remotely. The exploit has been made available to the public and could be exploited.

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-2025-9439?

It affects 1 product.


Products: 1000projects Online Student Project Report Submission and Evaluation System.

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

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

## Is CVE-2025-9439 being exploited?

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

## Other vulnerabilities in 1000projects Online Project Report Submission and Evaluation System

- [CVE-2025-10424](https://insights.sbomify.com/CVE-2025-10424/): 1000projects Online Student Project Report Submission and Evaluation System faculty_controller.php unrestricted upload (medium 6.9)
- [CVE-2025-10425](https://insights.sbomify.com/CVE-2025-10425/): 1000projects Online Student Project Report Submission and Evaluation System student_controller.php unrestricted upload (medium 6.9)
- [CVE-2025-9444](https://insights.sbomify.com/CVE-2025-9444/): 1000projects Online Project Report Submission and Evaluation System delete_group_student.php sql injection (medium 6.9)
- [CVE-2025-9434](https://insights.sbomify.com/CVE-2025-9434/): 1000projects Online Project Report Submission and Evaluation System edit_title.php cross site scripting (medium 5.3)
- [CVE-2025-9438](https://insights.sbomify.com/CVE-2025-9438/): 1000projects Online Project Report Submission and Evaluation System add_student.php cross site scripting (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-9439 is a medium-severity cross-site scripting vulnerability in 1000projects Online Project Report Submission and Evaluation System, published on 26 Aug 2025. An attacker can exploit it over the internet without logging in, 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-2025-9439 exists.

Affected product: 1000projects Online Project Report Submission and Evaluation 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-2025-9439/ (Markdown: https://insights.sbomify.com/CVE-2025-9439/index.md)
```

## Sources

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

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