CVE-2025-30073
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NSummary
CVE-2025-30073 is a high-severity Exposure of Data Element to Wrong Session (CWE-488) vulnerability in Syss (inferred from references). Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Web Session Cookie (T1550.004); ranked at the 27th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-30073 affects OPC cardsystems Webapp Aufwertung version 2.1.0, a web application used for loading funds onto employee cards. The vulnerability stems from the reuse of transaction references. When a payment is completed, the system processes the first or all transactions with the matching reference, depending on timing conditions. This business logic flaw, classified under CWE-488 (consistency of security controls across components), enables unauthorized over-crediting of funds.
The vulnerability carries a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), indicating it is exploitable over the network with low complexity by unauthenticated attackers requiring no user interaction. An attacker can initiate multiple transactions using the same reference and complete a single payment to trigger fulfillment of all associated transactions, resulting in more money being transferred to employee cards than was actually paid.
For mitigation guidance, refer to the advisory at https://www.syss.de/pentest-blog/businesslogik-fehler-bei-aufwertung-von-geldkarten-in-opcr-webapp-aufwertung-syss-2024-089.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-8261
Vulnerability Data
An issue was discovered in OPC cardsystems Webapp Aufwertung 2.1.0. The reference assigned to transactions can be reused. When completing a payment, the first or all transactions with the same reference are completed, depending on timing. This can be used…
more
to transfer more money onto employee cards than is paid.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
AC-3 enforces access decisions that can be scoped to the correct session context.
AC-4 controls information flows between entities, reducing cross-session leakage.
SC-4 directly stops unintended transfer of data through shared resources that different sessions may access.
SC-39 isolates execution domains so one session cannot reach another's state or data.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Enforcing authorization policies and least privilege can prevent cross-session data exposure when session separation is treated as an access rule.
Protecting data-in-use directly addresses runtime leakage of session data to unauthorized contexts.
Logical access controls and segmentation can be applied to isolate session state within applications or environments.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect the weakness but does not itself implement the preventive control.
Secure development lifecycle practices include session-management controls that prevent exposure of data to the wrong session.
Application security requirements explicitly call for proper session isolation and state management.
Secure system architecture principles require isolation of session state to avoid cross-session data leakage.
Secure coding standards mandate correct session handling to prevent exposure of data elements to the wrong session.
Information access restriction directly enforces session boundaries so data is not exposed to the wrong session.