# CVE-2026-114263: ProjectWorlds Advanced Library Management System individual_report_search.php mysqli_query 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:** 21 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-32h7-7653-xcf8

## What is CVE-2026-114263?

CVE-2026-114263 is a medium-severity vulnerability in ProjectWorlds Advanced Library Management System, published on 21 Oct 2026. 

### Official description

A vulnerability was identified in ProjectWorlds Advanced Library Management System 1.0. The affected element is the function mysqli_query of the file individual_report_search.php. Such manipulation of the argument roll_number leads to sql injection. The attack may be launched remotely. The exploit is publicly available and might be used.

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


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

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

## Is CVE-2026-114263 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114263 is a medium-severity vulnerability in ProjectWorlds Advanced Library Management System, published on 21 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114263 exists.

Affected product: ProjectWorlds Advanced Library Management 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-114263/ (Markdown: https://insights.sbomify.com/CVE-2026-114263/index.md)
```

## Sources

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

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