# CVE-2026-11960: Multiple vulnerabilities in FacturaScripts


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-jfpr-pfqx-2q8x

## What is CVE-2026-11960?

CVE-2026-11960 is a medium-severity vulnerability in FacturaScripts, published on 20 Oct 2026. 

### Official description

Enumeration of unauthenticated users in FacturaScripts, version 2025.61. The application returns different responses when attempting to log in with a valid username compared to an invalid one. An unauthenticated attacker could systematically identify valid usernames by examining variations in the application’s responses, such as changes in response time, discrepancies between error messages or differences in HTTP status codes. A successful exploit allows the attacker to compile a list of valid user accounts. This list could be used to carry out targeted brute-force attacks, password spraying, credential stuffing or social engineering campaigns against the confirmed accounts.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-11960 being exploited?

There is no known exploitation of CVE-2026-11960 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-11960 is a medium-severity vulnerability in FacturaScripts, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-11960 in the wild and no public exploit code.

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

## Sources

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

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