OpenSTAManager has a SQL Injection vulnerability in the Scadenzario bulk operations module
CVE-2026-24418GHSA-4xwv-49c8-fvhq
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-4xwv-49c8-fvhq 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-2026-24418: 0.40% estimated exploitation activity in the next 30 days; percentile 34.16 (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 Critical Error-Based SQL Injection vulnerability in the Scadenzario (Payment Schedule) bulk operations module of OpenSTAManager v2.9.8 allows authenticated attackers to extract complete database contents including user credentials, customer PII, and financial records through XML error messages. Status: ✅ Confirmed and tested on live instance (v2.9.8) Vulnerable Parameter: idrecords[] (POST array) Affected Endpoint: /actions.php?idmodule=18 (Scadenzario module) Attack Type: Error-Based SQL Injection (IN clause) Details OpenSTAManager v2.9.8 contains a critical Error-Based SQL Injection vulnerability in the bulk operations handler for the Scadenzario (Payment Schedule) module. The application fails to validate that elements of the idrecords array are integers before using them in an SQL IN() clause, allowing attackers to inject arbitrary SQL commands and extract sensitive data through XPATH error messages. Vulnerability Chain: 1. Entry Point: /actions.php (Lines 503-506) The…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-4xwv-49c8-fvhq
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-24418 Advisory: OpenSTAManager has a SQL Injection vulnerability in the Scadenzario bulk operations module IDs: CVE-2026-24418, GHSA-4xwv-49c8-fvhq Record: https://patchnext.com/advisories/cve-2026-24418 (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-4xwv-49c8-fvhq (GitHub-reviewed advisory GHSA-4xwv-49c8-fvhq lists affected ranges: Packagist devcode-it/openstamanager >=0 <=2.9.8) Commands are suggestions: review each one before running it.
Loading voting…