# CVE-2025-10411: itsourcecode E-Logbook with Health Monitoring System for COVID-19 POST Request check_profile.php cross site scripting

> Attackers can inject malicious scripts via the profile_id parameter in check_profile.php, potentially compromising user sessions and data.

- **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:** 14 Sep 2025
- **Updated:** 15 Sep 2025
- **Also known as:** GHSA-hg98-h2rq-79xr

## What is CVE-2025-10411?

CVE-2025-10411 is a medium-severity cross-site scripting vulnerability in itsourcecode E-Logbook with Health Monitoring System for COVID-19, published on 14 Sep 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 vulnerability was detected in itsourcecode E-Logbook with Health Monitoring System for COVID-19 1.0. This issue affects some unknown processing of the file /stc-log-keeper/check_profile.php of the component POST Request Handler. The manipulation of the argument profile_id results in cross site scripting. The attack may be launched remotely. The exploit is now public and may be used.

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-10411?

It affects 1 product.


Products: Emiloi E-Logbook With Health Monitoring System for Covid-19.

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

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

## Is CVE-2025-10411 being exploited?

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

## Other vulnerabilities in itsourcecode E-Logbook with Health Monitoring System for COVID-19

- [CVE-2026-3046](https://insights.sbomify.com/CVE-2026-3046/): itsourcecode E-Logbook with Health Monitoring System for COVID-19 check_profile_old.php sql injection (medium 6.9)
- [CVE-2025-10670](https://insights.sbomify.com/CVE-2025-10670/): itsourcecode E-Logbook with Health Monitoring System for COVID-19 check_profile.php sql injection (medium 6.9)
- [CVE-2025-10118](https://insights.sbomify.com/CVE-2025-10118/): itsourcecode E-Logbook with Health Monitoring System for COVID-19 login.php sql injection (medium 6.9)
- [CVE-2025-10614](https://insights.sbomify.com/CVE-2025-10614/): itsourcecode E-Logbook with Health Monitoring System for COVID-19 print_reports_prev.php cross site scripting (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10411 is a medium-severity cross-site scripting vulnerability in itsourcecode E-Logbook with Health Monitoring System for COVID-19, published on 14 Sep 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-10411 exists.

Affected product: itsourcecode E-Logbook with Health Monitoring System for COVID-19. 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-10411/ (Markdown: https://insights.sbomify.com/CVE-2025-10411/index.md)
```

## Sources

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

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