FacturaScripts has SQL Injection in Autocomplete Actions
CVE-2026-25514GHSA-pqqg-5f4f-8952
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (facturascripts/facturascripts 2025.81), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Packagist facturascripts/facturascripts
- Affected
- < 2025.81
- Fixed in
- 2025.81
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-pqqg-5f4f-8952 lists affected ranges: Packagist facturascripts/facturascripts >=0 <2025.81
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source
- EPSS
- CVE-2026-25514: 0.52% estimated exploitation activity in the next 30 days; percentile 44.54 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary FacturaScripts contains a critical SQL Injection vulnerability in the autocomplete functionality that allows authenticated attackers to extract sensitive data from the database including user credentials, configuration settings, and all stored business data. The vulnerability exists in the CodeModel::all() method where user-supplied parameters are directly concatenated into SQL queries without sanitization or parameterized binding. --- Details Multiple controllers in FacturaScripts, including CopyModel, ListController, and PanelController, implement an autocomplete action that processes user input through the CodeModel::search() or CodeModel::all() methods. These methods construct SQL queries by directly concatenating user-controlled parameters without any validation or escaping. Vulnerable Code Location File: /Core/Model/CodeModel.php Method: all() Lines: 108-109 Vulnerable Parameters The following parameters are vulnerable to SQL Injection: 1. source → Maps to $tableName -…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-pqqg-5f4f-8952
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-25514 Advisory: FacturaScripts has SQL Injection in Autocomplete Actions IDs: CVE-2026-25514, GHSA-pqqg-5f4f-8952 Record: https://patchnext.com/advisories/cve-2026-25514 (revision 1, source checked 26 Oct 2026, 14:35 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 8.7) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: facturascripts/facturascripts 2025.81. A vendor fix does not mean a deployment is fixed. ## Affected components - Packagist facturascripts/facturascripts: affected < 2025.81; fixed in 2025.81 ## Suggested inspection (read-only) - Packagist facturascripts/facturascripts: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on facturascripts/facturascripts. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-pqqg-5f4f-8952 (GitHub-reviewed advisory GHSA-pqqg-5f4f-8952 lists affected ranges: Packagist facturascripts/facturascripts >=0 <2025.81) Commands are suggestions: review each one before running it.
Loading voting…