# CVE-2026-116062: SourceCodester Performance Indicator System save_profile.php sql injection


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-w9gc-29p2-vj3j

## What is CVE-2026-116062?

CVE-2026-116062 is a medium-severity vulnerability in SourceCodester Performance Indicator System, published on 25 Oct 2026. 

### Official description

A security flaw has been discovered in SourceCodester Performance Indicator System 1.0. This issue affects some unknown processing of the file /opils/staff/save_profile.php. The manipulation of the argument Contact results in sql injection. The attack may be launched remotely. The exploit has been released to the public and may be used for attacks.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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


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

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

## Is CVE-2026-116062 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116062 is a medium-severity vulnerability in SourceCodester Performance Indicator System, published on 25 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-116062 exists.

Affected product: SourceCodester Performance Indicator 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-116062/ (Markdown: https://insights.sbomify.com/CVE-2026-116062/index.md)
```

## Sources

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

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