# CVE-2026-117515: oretnom23 php-travel-agency-system traceapplication.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:** 27 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-w5x8-f648-7ghf

## What is CVE-2026-117515?

CVE-2026-117515 is a medium-severity vulnerability in oretnom23 php-travel-agency-system, published on 27 Oct 2026. 

### Official description

A security flaw has been discovered in oretnom23 php-travel-agency-system 4e28b8f84d72420373dd15c3ae32900beb7e0635. Impacted is an unknown function of the file traceapplication.php. The manipulation of the argument Search results in sql injection. It is possible to launch the attack remotely. The exploit has been released to the public and may be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.

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


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

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

## Is CVE-2026-117515 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-117515 is a medium-severity vulnerability in oretnom23 php-travel-agency-system, published on 27 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-117515 exists.

Affected product: oretnom23 php-travel-agency-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-117515/ (Markdown: https://insights.sbomify.com/CVE-2026-117515/index.md)
```

## Sources

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

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