CVE-2025-61310
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 · uneditedA reflected cross-site scripted (XSS) vulnerability in the acc-menu_billings.php component of GmbH Mecury Managed Print Services (docuForm) v11.11c allows attackers to execute arbitrary Javascript in the context of a user's browser via injecting a crafted payload into an unfiltered variable value.
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 confidenceA reflected cross-site scripting (XSS) vulnerability exists in the acc-menu_billings.php component of GmbH Mecury Managed Print Services (docuForm) v11.11c. The vulnerability stems from an unfiltered variable that allows injection of malicious JavaScript payloads, which execute in the context of a victim's browser when the crafted request is processed.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 vulnerable PHP fileSearch the web server's document root for the file acc-menu_billings.php. Common paths may include /var/www/html/, /webroot/, or the application's include directory. Use a command like 'find / -name acc-menu_billings.php 2>/dev/null' or inspect the application directory structure.Affected if The file acc-menu_billings.php exists on the server and is part of the deployed docuForm application.
-
Verify the docuForm application versionCheck the installed version of Mecury Managed Print Services (docuForm). Look for version information in the application dashboard, about page, or configuration files. The affected version is v11.11c as indicated in the CVE summary.Affected if The installed version of docuForm is v11.11c.
-
Confirm web access to the billing moduleDetermine if the acc-menu_billings.php component is accessible via the web application. Attempt to access the URL path where billing functions are exposed, typically through an authenticated portal or billing interface.Affected if The acc-menu_billings.php script is accessible over HTTP/HTTPS and processes user requests.
-
Inspect the source code for unfiltered variablesReview the acc-menu_billings.php file for variables that are directly echoed or reflected in HTML output without sanitization. Look for $_GET, $_POST, or $_REQUEST parameters that are output without htmlspecialchars() or equivalent encoding.Affected if The PHP source contains unsanitized variable output that could be exploited for XSS injection.
You are affected if you are running docuForm v11.11c with the acc-menu_billings.php component accessible via the web and the source code contains unfiltered variables reflected in HTML output.
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 proper input validation and output encoding/escaping for all variable values rendered in acc-menu_billings.php to prevent XSS execution. The application should sanitize user-supplied data before reflecting it in HTML output.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-61310 — 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-61310 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