dbcve.org
OfbizApplication · Apache

CVE-2022-25370

MEDIUM · 5.4 CVSS v3.1 Published 2022-09-02
Fix available
A fix is available. Upgrade to 18.12.06 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Apache OFBiz uses the Birt plugin (https://eclipse.github.io/birt-website/) to create data visualizations and reports. In Apache OFBiz release 18.12.05, and earlier versions, by leveraging a vulnerability in Birt (https://bugs.eclipse.org/bugs/show_bug.cgi?id=538142), an unauthenticated malicious user could perform a stored XSS attack in order to inject a malicious payload and execute it using the stored XSS.

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

This is a stored XSS vulnerability in Apache OFBiz's Birt plugin integration. An unauthenticated attacker can inject malicious JavaScript payloads into Birt reports/visualizations that persist on the server and execute when other users view the affected content, due to insufficient input sanitization in the Birt component (Eclipse bug 538142).

MitigationUpgrade Apache OFBiz to a version that includes the patched Birt component, or disable the Birt plugin if not required, along with implementing output encoding for any report content rendering.

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:< 18.12.06

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify Apache OFBiz installation version
    Check the version file or build configuration (typically in VERSION, build.xml, or gradle.properties in the OFBiz root directory)
    Affected if Installed version is lower than 18.12.06
  2. Locate Birt plugin components
    Search for Birt-related files and directories in the OFBiz installation, such as 'birt' folders in the plugins or specialpurpose directories, and look for org.eclipse.birt runtime jars
    Affected if Birt plugin directory or birt*.jar files exist in the installation
  3. Verify Birt is configured or accessible
    Inspect the OFBiz controller.xml files within Birt plugin directories (commonly in specialpurpose/birt) and check if there are any webapp mappings or services configured for Birt
    Affected if Birt controller configurations exist and the webapp is mapped to a URL endpoint
  4. Check for unauthenticated Birt endpoints
    Review web.xml or controller.xml in the Birt plugin to identify any URL patterns that may be accessible without authentication
    Affected if Birt report viewer or rendering endpoints are mapped without requiring authentication
  5. Determine if Birt reports can accept user input
    Inspect Birt report templates (.rptdesign files) or look for parameters in the Birt plugin that accept user-supplied data for report generation
    Affected if The Birt plugin accepts URL parameters or form inputs that could be used to inject malicious content

You are affected if your Apache OFBiz version is below 18.12.06 AND the Birt plugin is installed and accessible, as the insufficient sanitization in the Birt component allows stored XSS injection into reports.

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

Upgrade Apache OFBiz to a version that includes the patched Birt component, or disable the Birt plugin if not required, along with implementing output encoding for any report content rendering.

Recommended fix Moderate confidence

18.12.06

  1. Backup your existing OFBiz installation and database before upgrading
  2. Download Apache OFBiz version 18.12.06 from the official Apache repository (https://ofbiz.apache.org/download.html)
  3. Stop the running OFBiz services
  4. Replace the existing OFBiz installation with the new 18.12.06 version
  5. Review and update any custom configurations or plugins that may be affected by the upgrade
  6. Start the OFBiz services and verify the application is running correctly
  7. Test the Birt plugin functionality to ensure reports and visualizations are working as expected
Caveat Review Apache OFBiz release notes for 18.12.06 to check for any configuration or API changes that may affect custom implementations

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

Fix this in Ofbiz Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
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,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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