CVE-2026-5699 Stored Cross-Site Scripting (XSS) vulnerability in SABBATIC application
Medium 4.8
Published
Updated
Check this codebase for CVE-2026-5699 and fix it if it is affected.
What it is: CVE-2026-5699 is a medium-severity vulnerability in SABBATIC app, published on 29 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-5699 in the wild and no public exploit code.
Affected product: SABBATIC app. 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-5699/ (Markdown: https://insights.sbomify.com/CVE-2026-5699/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-5699?
CVE-2026-5699 is a medium-severity vulnerability in SABBATIC app, published on 29 Oct 2026.
Official description
Stored Cross-Site Scripting (XSS) vulnerability in SABBATIC application that allows an attacker to store JavaScript code so that when a user views the page, code can be executed in the victim's browser. The list of assigned parameters and identifiers is as follows: parameter 'companyName' in /empresa endpoint;
Weakness: CWE-79
Which versions are affected by CVE-2026-5699?
How do I fix CVE-2026-5699?
No fix has been published for CVE-2026-5699 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-5699 being exploited?
There is no known exploitation of CVE-2026-5699 in the wild and no public exploit code.
Sources
Also known as GHSA-qx7c-rf9h-6rrg.