VulnerabilityPublished 8 Jan 2026Updated 11 Feb 2026

CVE-2025-61546: CVE-2025-61546 is a critical

Source CVE Database V5

Not known to be exploited · CVSS 9.1 Critical · fixed in 19.69 : patch affected systems as a priority.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

9.1Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 19.69

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Immediate upgrade to edu Business Solutions Print Shop Pro WebDesk version 19.69 or later, where the vulnerability is fixed.
Implement strict server-side input validation to enforce quantity constraints and reject negative or otherwise invalid values regardless of client input.
Conduct thorough code reviews and security testing focusing on input validation and transaction processing endpoints.
Monitor transaction logs for unusual patterns such as negative quantities or credits that could indicate exploitation attempts.
Employ web application firewalls (WAFs) with custom rules to detect and block suspicious requests targeting the vulnerable endpoint.
Educate development and operations teams about the risks of relying solely on client-side validation and the importance of defense in depth.
Review and enhance financial reconciliation processes to quickly identify and respond to anomalies.
Coordinate with vendors for timely security updates and advisories.

Description

CVE-2025-61546 is a critical vulnerability in edu Business Solutions Print Shop Pro WebDesk version 18.34 that allows remote attackers to manipulate financial transactions by submitting negative quantities when purchasing items. This flaw exists because the application relies solely on client-side input validation, which can be bypassed, enabling attackers to create financial discrepancies. The vulnerability is exploitable without authentication or user interaction, with a CVSS score of 9.1 indicating high impact on confidentiality and integrity. It was fixed in version 19.69. European organizations using affected versions risk financial fraud and data integrity issues. Mitigation requires upgrading to the patched version and implementing robust server-side input validation. Countries with significant adoption of edu Business Solutions products and strong print service sectors, such as Germany, France, and the UK, are most likely to be impacted.

Impact

For European organizations, this vulnerability poses a significant risk of financial fraud and data integrity compromise. Attackers exploiting this flaw can manipulate purchase transactions to create negative charges, potentially leading to unauthorized credits or financial losses for the organization. This can disrupt accounting processes, damage trust with customers and partners, and result in regulatory compliance issues, especially under GDPR where financial data integrity is critical. Print shops and businesses relying on edu Business Solutions Print Shop Pro WebDesk for transaction processing are particularly vulnerable. The lack of authentication requirement and ease of exploitation increase the likelihood of attacks, which could be automated and widespread. Financial discrepancies could also be used as a vector for further fraud or to mask other malicious activities. The impact extends beyond direct financial loss to reputational damage and potential legal liabilities in the European market.

Summary

CVE-2025-61546 is a critical security vulnerability identified in edu Business Solutions Print Shop Pro WebDesk version 18.34, specifically affecting the /PSP/appNET/Store/CartV12.aspx/GetUnitPrice endpoint. The flaw arises from the application's reliance on client-side input validation to enforce quantity constraints during purchase transactions. Attackers can exploit this by submitting negative quantities for items, which the server fails to properly validate, leading to financial discrepancies such as negative charges or credits. This vulnerability compromises the integrity and confidentiality of financial data, as attackers can manipulate transaction records remotely without requiring authentication or user interaction. The vulnerability is classified under CWE-20 (Improper Input Validation), highlighting the failure to validate input on the server side. The CVSS v3.1 base score of 9.1 reflects the ease of exploitation (network attack vector, low complexity), no privileges required, no user interaction, and high impact on confidentiality and integrity, though availability is unaffected. Although no known exploits are reported in the wild yet, the critical nature and straightforward exploitation method make this a significant threat. The issue was addressed in version 19.69 of the software, emphasizing the need for timely patching. Organizations using version 18.34 or earlier should prioritize remediation to prevent potential financial fraud and data integrity violations.

CWE-20Improper Input Validation (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #18OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Attack Surface Reduction
Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build "recognizers" for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of…
Architecture and Design · Libraries or Frameworks
Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any…
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Buffer Overflow via Environment Variables (opens in a new tab)
Server Side Include (SSI) Injection (opens in a new tab)
Cross Zone Scripting (opens in a new tab)
Command Line Execution through SQL Injection (opens in a new tab)
Object Relational Mapping Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/chndlrx/vulnerability-disclosures/tree/main/CVE-2025-61546 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 18 Feb 2026, 15:13 UTC

WeaknessesCWE-20

Technical details

References

Community reviews

Related threats