CVE-2025-61313
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 dfm-menu_markeralerts.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 · moderate confidenceA reflected cross-site scripting (XSS) vulnerability exists in the dfm-menu_markeralerts.php component of GmbH Mercury Managed Print Services (docuForm) v11.11c. The vulnerability stems from an unfiltered variable being reflected back to the user without proper input sanitization or output encoding, allowing attackers to inject arbitrary JavaScript that executes in the victim's browser session.
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
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/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.
-
Confirm docuForm installation and versionLocate the docuForm installation directory and check the version file or banner. Common methods: look for version.txt, check HTTP server headers, or examine the application footer for version information.Affected if The installed version matches v11.11c or falls within the affected version range of docuForm.
-
Locate the vulnerable scriptSearch for the file dfm-menu_markeralerts.php within the docuForm web root directory.Affected if The file dfm-menu_markeralerts.php exists in the web-accessible directory.
-
Verify the script is accessible via HTTPAttempt to access the file directly through the web server (e.g., GET request to /dfm-menu_markeralerts.php). Check if the script responds to HTTP requests.Affected if The script is reachable via HTTP and processes requests without authentication requirements.
-
Inspect HTTP response for unfiltered parameter reflectionSend a crafted request with a test payload in potential parameters (e.g., ?param=<script>alert(1)</script>) and examine if the script reflects the input back unescaped in the response.Affected if The response contains the unsanitized test payload, indicating the parameter is reflected without output encoding.
-
Check for existing exploitation indicatorsReview web server access logs and application logs for suspicious requests containing script tags, javascript:, or other XSS payloads to the dfm-menu_markeralerts.php endpoint.Affected if Log analysis reveals suspicious requests with XSS payloads targeting this endpoint.
You are affected if you are running docuForm v11.11c, the dfm-menu_markeralerts.php file exists and is web-accessible, and the vulnerable parameter reflects user input without 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 proper input validation and output encoding for all user-supplied data in the affected component. The vendor should release a patch for docuForm v11.11c that sanitizes the vulnerable parameter before reflecting it in the HTTP response.
- 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-61313 — 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-61313 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