CVE-2026-82902 · Package
NO FIX YET · SEE WHAT TO DO
A logged-in user with the WebTools view permission can make the OFBiz server send requests to arbitrary URLs by supplying a parameter to the viewdatafile screen. An attacker who also holds entity and datafile maintenance permissions can read arbitrary local files through a file: URL.
first public Nov 5, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams running Apache OFBiz 24.09 releases before 24.09.08 on any platform. Exposure is greatest where accounts with the WebTools view permission exist and the server can reach internal networks or local files. Instances on other OFBiz versions are not stated as affected.
Not affected if versions-24.09.08-or-later
Who cares apache-ofbiz, java, self-hosted
24.09.08.viewdatafile screen and ViewDataFile.groovy in the deployed OFBiz webtools component.24.09.08.Server-Side Request Forgery in ViewDataFile in Apache OFBiz 24.09 before 24.09.08 on all platforms allows a remote authenticated attacker holding only the base webtools permissions (OFBTOOLS_VIEW, WEBTOOLS_VIEW) to cause the server to issue arbitrary outbound HTTP requests, and an attacker additionally holding ENTITY_MAINT and DATAFILE_MAINT to read arbitrary local files via a file: URL, by supplying the DEFINITION_LOCATION or DATAFILE_LOCATION request parameter to the viewdatafile screen, because ViewDataFile.groovy dereferences both parameters as java.net.URL objects with no scheme allow-list, host filter, or egress control inside a screen action that runs before the screen's and template's permission checks are evaluated, so the fetch executes regardless of whether the requesting account is authorized to view its result. Users are recommended to upgrade to version 24.09.08, which fixes this issue.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.