dbcve.org
Infinity ZmaintenanceApplication · Zucchetti

CVE-2025-61431

MEDIUM · 6.1 CVSS v3.1 Published 2025-11-04
Fix available
A fix is available. Upgrade to after 4.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
A reflected cross-site scripted (XSS) vulnerability in the /jsp/gsfr_feditorHTML.jsp endpoint of Zucchetti ZMaintenance Infinity and Infinity Zucchetti v4.1 and earlier allows attackers to execute arbitrary Javascript in the context of a user's browser via injecting a crafted payload into the pHtmlSource parameter. A vendor fix was released on 2025-06-18.

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 confidence

A reflected cross-site scripting (XSS) vulnerability in the /jsp/gsfr_feditorHTML.jsp endpoint of Zucchetti ZMaintenance Infinity allows attackers to inject malicious JavaScript via the pHtmlSource parameter. When a user visits a crafted URL, the attacker's script executes in their browser context.

MitigationApply the vendor fix released on 2025-06-18. If immediate patching is not feasible, implement input validation and output encoding on the pHtmlSource parameter to neutralize script injection attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Infinity ZmaintenanceApplication
Affected:<= 4.1
Infinity ZucchettiApplication
Affected:<= 4.1

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Zucchetti Infinity version
    Locate the Zucchetti Infinity installation and check the version information, typically found in the application header, about page, or installation directory metadata
    Affected if The installed version is Zmaintenance or Zucchetti Infinity at version 4.1 or lower
  2. Confirm /jsp/gsfr_feditorHTML.jsp endpoint is accessible
    Attempt to access the endpoint via HTTP/HTTPS: http(s)://<host>/jsp/gsfr_feditorHTML.jsp
    Affected if The endpoint responds with any content, indicating it is exposed and potentially vulnerable
  3. Check if pHtmlSource parameter is accepted without encoding
    Send a test request to the endpoint with a benign XSS payload in the pHtmlSource parameter, such as ?pHtmlSource=<script>alert(1)</script>, and observe if the script tags are reflected unescaped in the response
    Affected if The response contains the raw script tags or other unsanitized input from the pHtmlSource parameter, indicating the vulnerability is present
  4. Review web application firewall or input validation logs
    Examine WAF logs, application logs, or proxy logs for any blocked requests related to the gsfr_feditorHTML.jsp endpoint or pHtmlSource parameter
    Affected if No blocks or sanitization are observed for XSS payloads in the pHtmlSource parameter

A user is affected if they run Zmaintenance or Zucchetti Infinity at version 4.1 or lower AND the /jsp/gsfr_feditorHTML.jsp endpoint is accessible AND the pHtmlSource parameter reflects input without HTML encoding.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 4.1
Interim mitigation

Apply the vendor fix released on 2025-06-18. If immediate patching is not feasible, implement input validation and output encoding on the pHtmlSource parameter to neutralize script injection attempts.

Recommended fix Moderate confidence

Version after 4.1 that includes the 2025-06-18 vendor security fix (contact Zucchetti for exact version number)

  1. Contact Zucchetti vendor support or visit the official Zucchetti support portal to obtain the security patch released on 2025-06-18
  2. Apply the vendor patch to all affected Infinity Zmaintenance installations (version <= 4.1)
  3. Apply the vendor patch to all affected Infinity Zucchetti installations (version <= 4.1)
  4. Verify the patch was successfully applied by confirming the /jsp/gsfr_feditorHTML.jsp endpoint no longer accepts malicious pHtmlSource payloads
  5. Test that legitimate functionality of the gsfr_feditorHTML.jsp endpoint still works as expected
Caveat Unknown from provided material; contact vendor for release notes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Infinity Zmaintenance Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-61431 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-61431 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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