OpenSTAManager has a SQL Injection in Scadenzario Print Template
CVE-2025-69216GHSA-q6g3-fv43-m2w6
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
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 devcode-it/openstamanager
- Affected
- <= 2.9.8
- Fixed in
- no fixed version recorded
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-q6g3-fv43-m2w6 lists affected ranges: Packagist devcode-it/openstamanager >=0 <=2.9.8
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-2025-69216: 0.39% estimated exploitation activity in the next 30 days; percentile 33.52 (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 An authenticated SQL Injection vulnerability in OpenSTAManager's Scadenzario (Payment Schedule) print template allows any authenticated user to extract sensitive data from the database, including admin credentials, customer information, and financial records. The vulnerability enables complete database read access through error-based SQL injection techniques. Details The vulnerability exists in templates/scadenzario/init.php at line 46, where the idanagrafica parameter is directly concatenated into an SQL query without proper sanitization: Vulnerable Code: The get() function retrieves user input from GET/POST parameters without validation. The parameter value is directly embedded into the SQL query string using string concatenation instead of using the application's prepare() sanitization function, enabling SQL Injection attacks. Root Cause: - Missing use of prepare() function for input sanitization - Direct string concatenation in SQL query construction - No input validation…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-q6g3-fv43-m2w6
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-2025-69216 Advisory: OpenSTAManager has a SQL Injection in Scadenzario Print Template IDs: CVE-2025-69216, GHSA-q6g3-fv43-m2w6 Record: https://patchnext.com/advisories/cve-2025-69216 (revision 1, source checked 26 Oct 2026, 14:38 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 response not established. A vendor fix does not mean a deployment is fixed. ## Affected components - Packagist devcode-it/openstamanager: affected <= 2.9.8 ## Suggested inspection (read-only) - Packagist devcode-it/openstamanager: check the installed version with your package manager. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on devcode-it/openstamanager. - 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-q6g3-fv43-m2w6 (GitHub-reviewed advisory GHSA-q6g3-fv43-m2w6 lists affected ranges: Packagist devcode-it/openstamanager >=0 <=2.9.8) Commands are suggestions: review each one before running it.
Loading voting…