OpenSTAManager has an SQL Injection in the Stampe Module

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-69215: 0.44% estimated exploitation activity in the next 30 days; percentile 38.69 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Vulnerability Details Location - File: modules/stampe/actions.php - Line: 26 - Vulnerable Code: Root Cause The module parameter from POST data is directly concatenated into an SQL UPDATE query without using the prepare() sanitization function. While the predefined parameter is validated with intval(), the module parameter only has an !empty() check, which does NOT prevent SQL injection. Vulnerable Pattern: Exploitation Vulnerable Endpoint Required Parameters Authentication Requirement - Requires valid authenticated session (any user with access to Stampe module) - VERIFIED: Users with "Tecnici" group access can exploit (NOT admin-only!) - PoC: Demo at https://demo.osmbusiness.it with credentials tecnico/tecnicotecnico Exploitation Type Error-based SQL Injection using MySQL's EXTRACTVALUE/UPDATEXML/GTIDSUBSET functions Proof of Concept Method 1: EXTRACTVALUE (MySQL 5.1+) Result: <img width="2208" height="912" alt="image"…

Published by the source

3 Feb 2026, 19:01 UTC

Last modified by the source

4 Feb 2026, 19:53 UTC

Source last checked

26 Oct 2026, 14:35 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-qx9p-w3vj-q24q

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-69215

Advisory: OpenSTAManager has an SQL Injection in the Stampe Module
IDs: CVE-2025-69215, GHSA-qx9p-w3vj-q24q
Record: https://patchnext.com/advisories/cve-2025-69215 (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 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-qx9p-w3vj-q24q (GitHub-reviewed advisory GHSA-qx9p-w3vj-q24q lists affected ranges: Packagist devcode-it/openstamanager >=0 <=2.9.8)

Commands are suggestions: review each one before running it.