CVE-2025-2313
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn the Print.pl service, the "uhcPrintServerPrint" function allows execution of arbitrary code via the "CopyCounter" parameter.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Print.pl service contains a command injection vulnerability in the 'uhcPrintServerPrint' function. The 'CopyCounter' parameter is not properly validated before being used in a system call, allowing an attacker to inject and execute arbitrary operating system commands.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the Print.pl serviceSearch for the Print.pl file in the web server's cgi-bin or scripts directory, or identify the service/process that handles print requestsAffected if Print.pl is present and accessible on the system
-
Identify the product containing Print.plCheck the application or appliance that includes the Print.pl component (e.g., check the parent application, service banner, or documentation)Affected if The product is a print management or document handling system that includes Print.pl
-
Check if the uhcPrintServerPrint function is exposedReview the Print.pl source code or configuration to determine if the uhcPrintServerPrint function is enabled and accessible via HTTP/HTTPS requestsAffected if The uhcPrintServerPrint function is enabled and reachable over the network
-
Verify network accessibility of the CopyCounter parameterDetermine if the Print.pl endpoint accepts the CopyCounter parameter through HTTP GET or POST requests (e.g., test with a benign query string)Affected if The CopyCounter parameter can be supplied as input to the Print.pl service over the network
-
Compare installed version to any known affected versionsCheck the product version (typically via --version flag, web interface, or configuration file) and compare to any vendor-specified affected version rangesAffected if The installed version falls within an affected range (if known) or is an unpatched version of the product
The system is affected if the Print.pl service is running, the uhcPrintServerPrint function is enabled, and the CopyCounter parameter is accessible over the network without proper sanitization.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict input validation on the CopyCounter parameter to ensure only valid numeric values are accepted, or use parameterized queries/prepared statements to prevent command injection. Apply the vendor patch immediately given the critical CVSS score.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2313 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-2313 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data