dbcve.org
OfbizApplication · Apache

CVE-2025-61623

MEDIUM · 6.5 CVSS v3.1 Published 2025-11-12
Fix available
A fix is available. Upgrade to 24.09.03 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Reflected cross-site scripting vulnerability in Apache OFBiz. This issue affects Apache OFBiz: before 24.09.03. Users are recommended to upgrade to version 24.09.03, which fixes the issue.

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 confidence

Reflected cross-site scripting (XSS) vulnerability in Apache OFBiz allows attackers to inject malicious scripts via unsanitized user input that gets reflected back in the HTTP response. The vulnerability is exploitable through crafted URLs containing malicious payload.

MitigationUpgrade to Apache OFBiz version 24.09.03 or later, which contains the security fix. Until upgraded, implement output encoding and input validation on affected endpoints as a compensating control.

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
OfbizApplication
Affected:< 24.09.03

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Locate and identify the OFBiz installation
    Find the OFBiz installation directory on the system. Common locations include /opt/ofbiz, /usr/local/ofbiz, or within an application server's webapps directory. Identify the war file or unpacked application folder.
    Affected if Apache OFBiz is installed on the system
  2. Determine the installed OFBiz version
    Check the version file in the OFBiz installation. Look for a VERSION file in the root directory, or examine the build.gradle file. If deployed on an application server, the version may be visible in the war filename or manifest.mf file inside the war archive.
    Affected if The identified version is lower than 24.09.03
  3. Verify the OFBiz web interface is accessible
    Confirm the OFBiz web application is running by accessing its base URL on the configured port (commonly port 8080). Attempt to reach common endpoints like the login page or main control portal.
    Affected if The OFBiz web interface is accessible over the network

The environment is affected if Apache OFBiz version is identified as lower than 24.09.03 and the web interface is accessible, making the reflected XSS exploitable via crafted URLs.

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 24.09.03 or later
Fixed in 24.09.03
Interim mitigation

Upgrade to Apache OFBiz version 24.09.03 or later, which contains the security fix. Until upgraded, implement output encoding and input validation on affected endpoints as a compensating control.

Recommended fix High confidence

24.09.03

  1. Backup the existing OFBiz installation and database before starting the upgrade process
  2. Stop the currently running OFBiz service
  3. Download Apache OFBiz version 24.09.03 from the official Apache OFBiz distribution (https://ofbiz.apache.org/download.html)
  4. Extract the new version to a temporary location
  5. Copy custom configurations, plugins, and data from the old installation to the new version, preserving local changes
  6. Replace the old OFBiz installation directory with the new 24.09.03 version
  7. Start the OFBiz service
  8. Verify the installation by accessing the OFBiz web interface and checking that the XSS vulnerability is resolved
Caveat Review the OFBiz 24.09.03 release notes for any breaking changes or deprecations that may affect custom configurations or integrations

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

Fix this in Ofbiz Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-61623 — 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-61623 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