# CVE-2026-125078: SourceCodester Smart Attendance System with QR Code Scanner login.php session fixiation


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-4wvj-gj48-qj5w

## What is CVE-2026-125078?

CVE-2026-125078 is a medium-severity vulnerability in SourceCodester Smart Attendance System with QR Code Scanner, published on 10 Nov 2026. 

### Official description

A security flaw has been discovered in SourceCodester Smart Attendance System with QR Code Scanner 1.0. This affects an unknown part of the file login.php. The manipulation results in session fixiation. The attack can be launched remotely. The exploit has been released to the public and may be used for attacks.

Weakness: CWE-384 (Session Fixation)

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


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

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

## Is CVE-2026-125078 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-125078 is a medium-severity vulnerability in SourceCodester Smart Attendance System with QR Code Scanner, published on 10 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-125078 exists.

Affected product: SourceCodester Smart Attendance System with QR Code Scanner. 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-125078/ (Markdown: https://insights.sbomify.com/CVE-2026-125078/index.md)
```

## Sources

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

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