CVE-2026-83542: Apache OFBiz Remote Code Execution via Screen Descriptor Widget-Resource Injection
A critical unauthenticated remote code execution vulnerability in Apache OFBiz (CVE-2026-83542, CVSS 9.8) enables external adversaries to execute arbitrary Java and Groovy commands across enterprise ERP, procurement, and e-commerce platforms. By issuing a multipart HTTP POST request to pre-authentication endpoints while specifying an untrusted XML screen layout via the mainDecoratorLocation parameter, attackers force the MacroScreenRenderer to evaluate embedded Groovy expressions without sandboxing. This grants immediate root/daemon system access, enabling mass exfiltration of financial ledgers, customer records, and PCI-DSS assets. Hermes scores CVE-2026-83542 at HTS 97 (CRITICAL).
HERMES THREAT SCORE & ENTERPRISE ERP RUNTIME INTEGRITY
Target:Apache OFBiz Screen Rendering Architecture (ScreenFactory / MacroScreenRenderer / Groovy Script Evaluator) [object Object]
1. Executive Summary & Threat Telemetry
Section titled โ1. Executive Summary & Threat TelemetryโIn November 2026, the Apache Software Foundation (ASF) released a critical security bulletin disclosing CVE-2026-83542, an unauthenticated remote code execution vulnerability impacting Apache OFBiz versions prior to 24.09.08. The flaw is classified under CWE-94 (Improper Control of Generation of Code) and has been assigned a CVSS v3.1 score of 9.8 (CRITICAL).
Threat research published by VulnCheck and security analysts tracking enterprise initial access brokers reveals that functional exploit chains are circulating in underground forums. Apache OFBiz powers business-critical Enterprise Resource Planning (ERP), inventory management, and customer relationship software across global logistics, government procurement, and large retail enterprises.
The flaw allows an unauthenticated remote attacker to submit a multipart HTTP POST request that uploads a small XML screen descriptor and immediately points the view parameter mainDecoratorLocation to the temporary file descriptor. As OFBiz renders the response, the widget engine evaluates the XML, executing arbitrary Java/Groovy code directly within the web container process.
flowchart TD subgraph Attacker["Adversary Operations"] Req["HTTP POST Multipart Request\n(Injects mainDecoratorLocation)"] Payload["Crafted XML Screen Descriptor\n<actions><set field='...' value='${groovy:...}'/></actions>"] end
subgraph OFBiz["Apache OFBiz Application Server"] Servlet["ControlServlet / RequestHandler"] TempFile["Temporary Upload Stream\n/tmp/ofbiz_upload_*.tmp"] Factory["ScreenFactory.getScreenFromLocation()"] Renderer["MacroScreenRenderer"] GroovyEngine["Groovy Scripting Engine\n(Unsandboxed Evaluation)"] end
subgraph Target["Enterprise Host System"] Shell["System Command Execution\n(/bin/sh / ProcessBuilder)"] Database["ERP PostgreSQL / MySQL Database\n(Financial Records / Credentials)"] end
Req --> Servlet Payload --> TempFile Servlet -->|Resolves mainDecoratorLocation| Factory Factory -->|Reads Descriptor| TempFile Factory --> Renderer Renderer --> GroovyEngine GroovyEngine --> Shell Shell --> Database2. Architectural Root Cause & Vulnerability Decomposition
Section titled โ2. Architectural Root Cause & Vulnerability DecompositionโApache OFBiz features an extensible UI layout engine driven by XML โscreensโ and โdecoratorsโ. In OFBiz, a screen defines page structures and data models, while a decorator supplies standardized navigational wrappers:
<screen name="main-decorator"> <section> <actions> <!-- Actions executed during screen preparation --> </actions> <widgets> <!-- Renderable widgets --> </widgets> </section></screen>When handling inbound HTTP requests, the OFBiz RequestHandler maps URLs to view handlers defined in controller.xml. Several standard controllers accept request parameters allowing callers to dynamically select layout themes, including mainDecoratorLocation.
In vulnerable releases of ModelScreen.java and ScreenFactory.java:
public static ModelScreen getScreenFromLocation(String combinedName) throws IOException, SAXException, ParserConfigurationException {
String resourceName = ScreenFactory.getResourceNameFromCombined(combinedName); String screenName = ScreenFactory.getScreenNameFromCombined(combinedName);
// VULNERABILITY: Resource resolution does not restrict URL protocols or file paths! // Accepts file:, http:, or absolute filesystem paths without canonicalization check. URL screenFileUrl = FlexibleLocation.resolveLocation(resourceName);
return getScreenFromLocation(screenFileUrl, screenName);}When an attacker uploads a multipart form containing an XML file, the servlet container writes the incoming stream into a temporary directory (e.g., /tmp/). By supplying mainDecoratorLocation=file:/tmp/ofbiz_upload_xxx.tmp#main-decorator, the attacker forces ScreenFactory to parse their uploaded XML as an OFBiz screen.
The MacroScreenRenderer processes <actions> blocks within the uploaded screen:
<screen name="main-decorator"> <section> <actions> <set field="exec" value="${groovy:'java.lang.Runtime.getRuntime().exec(\"id\")'}"/> </actions> <widgets> <platform-specific><html><html-template><![CDATA[pwned]]></html-template></html></platform-specific> </widgets> </section></screen>Because OFBiz evaluates string expressions prefixed with ${groovy:...} using the Apache Groovy shell without class whitelisting or AST sandbox transformations, the injected script executes with the full privileges of the application runtime.
3. Attack Vectors & Exploit Chain Mechanics
Section titled โ3. Attack Vectors & Exploit Chain MechanicsโStage 1: Anonymous Target Reconnaissance
Section titled โStage 1: Anonymous Target ReconnaissanceโThe attacker identifies exposed Apache OFBiz endpoints by querying standard URI paths (/control/login, /sfa/control/editPortalPageColumnWidth, or /ecommerce/control/main). The presence of OFBiz.Visitor cookies or server headers confirms vulnerable instances.
Stage 2: Staging the Multipart Payload
Section titled โStage 2: Staging the Multipart PayloadโThe attacker crafts a single multipart HTTP POST request carrying:
- A file parameter containing the XML screen definition with the embedded Groovy payload.
- A URL parameter
mainDecoratorLocationpointing to the temporary file path or an internal URI handler.
Stage 3: Unsandboxed Groovy Invocation
Section titled โStage 3: Unsandboxed Groovy InvocationโAs ControlServlet invokes MacroScreenRenderer, the screen renderer instantiates GroovyUtil.eval(). The payload executes a reverse shell or writes a persistent JSP web shell into the webapp directory (applications/content/webapp/content/pwn.jsp).
Stage 4: Database Dumping & Lateral Movement
Section titled โStage 4: Database Dumping & Lateral MovementโThe attacker extracts database credentials from framework/entity/config/entityengine.xml, queries the backend PostgreSQL/MySQL database, and dumps sensitive transactional data, supplier invoices, and employee records.
sequenceDiagram autonumber actor Attacker as Threat Actor participant Web as OFBiz ControlServlet (:8443) participant Temp as Filesystem (/tmp/) participant Engine as Screen Engine & Groovy participant DB as Backend Database
Attacker->>Web: POST /sfa/control/editPortalPageColumnWidth<br/>(Multipart Form with XML + mainDecoratorLocation) Web->>Temp: Stream Uploaded File to /tmp/upload_1337.xml Web->>Engine: Render Screen (mainDecoratorLocation = file:/tmp/upload_1337.xml) Engine->>Temp: Parse upload_1337.xml Engine->>Engine: Execute <set field="..." value="${groovy:...}"/> Note over Engine: Unsandboxed Groovy execution triggers reverse shell! Engine-->>Attacker: Connection Established (UID: ofbiz) Attacker->>DB: Query Financial Records & Hash Dumps Note over DB: Enterprise ERP Compromise Complete4. Real-World Weaponization & Threat Actor Profiling
Section titled โ4. Real-World Weaponization & Threat Actor ProfilingโVulnCheck telemetry and open-source intelligence track rapid weaponization of CVE-2026-83542:
- Initial Access Brokers (IABs): IABs are scanning IPv4 space for exposed Apache OFBiz endpoints. Upon successful compromise, brokers establish persistent SSH keys or web shells and auction off footholds on illicit underground markets.
- ERP Supply-Chain Extortion: Advanced ransomware operators target ERP backends because encrypting enterprise resource planning software halts logistics, shipping, and order fulfillment, creating extreme pressure on victims to pay extortion demands.
- Exploit Chaining with CVE-2026-82907: Attackers leverage
externalLoginKeycapture-replay flaws to maintain persistent administrative session tokens without authenticating through perimeter SAML/SSO gateways.
5. Detection Engineering & Triage
Section titled โ5. Detection Engineering & Triageโtitle: Apache OFBiz Screen Descriptor Groovy RCE Attemptid: b341e972-8411-4389-9801-cve202683542status: experimentaldescription: Detects HTTP requests to Apache OFBiz containing mainDecoratorLocation parameters pointing to file URI schemes or temporary directories.references: - https://lists.apache.org/thread/w225whj3z2rmq1h13b28b7j8f307584r - https://nvd.nist.gov/vuln/detail/CVE-2026-83542author: Hermes Codex Cyber Defense Teamdate: 2026-11-08logsource: category: webserver product: apache_ofbizdetection: selection_param: cs-uri-query|contains: - 'mainDecoratorLocation=file:' - 'mainDecoratorLocation=/tmp/' - 'mainDecoratorLocation=http:' - 'mainDecoratorLocation=https:' selection_post: cs-method: 'POST' cs-uri-stem|contains: - '/control/' - '/sfa/' - '/catalog/' condition: selection_param or (selection_post and selection_param)falsepositives: - None expected for external clients supplying file: or http: decorator schemes.level: criticaltags: - attack.initial_access - attack.t1190 - attack.t1059 - cve.2026.83542// Detect Apache OFBiz Groovy Injection via Web Logs & Process Creationlet SuspiciousURIs = W3CIISLog| where csUriStem has "/control/"| where csUriQuery has_any ("mainDecoratorLocation=file:", "mainDecoratorLocation=/tmp/", "mainDecoratorLocation=http:")| project TimeGenerated, cIP, csMethod, csUriStem, csUriQuery, scStatus;let ProcessEvents = DeviceProcessEvents| where InitiatingProcessFileName has "java" and InitiatingProcessCommandLine has "ofbiz"| where FileName in~ ("sh", "bash", "cmd.exe", "powershell.exe", "curl", "wget", "nc")| project TimeGenerated, DeviceName, FileName, ProcessCommandLine, InitiatingProcessCommandLine;SuspiciousURIs| join kind=inner (ProcessEvents) on $left.TimeGenerated between (ProcessEvents.TimeGenerated - 2m .. ProcessEvents.TimeGenerated + 2m)| project TimeGenerated, cIP, csUriStem, csUriQuery, FileName, ProcessCommandLinealert http $EXTERNAL_NET any -> $HOME_NET [8080,8443] ( msg:"HERMES - Apache OFBiz Screen Descriptor Groovy RCE Attempt (CVE-2026-83542)"; flow:established,to_server; http.uri; content:"mainDecoratorLocation="; nocase; pcre:"/mainDecoratorLocation=(file|http|https|\/tmp)/i"; classtype:web-application-attack; sid:202683542; rev:1; metadata:cve CVE-2026-83542, severity critical;)index=web sourcetype="access_combined"(uri_query="*mainDecoratorLocation=file:*" OR uri_query="*mainDecoratorLocation=/tmp/*" OR uri_query="*mainDecoratorLocation=http:*")| stats count earliest(_time) as first_seen latest(_time) as last_seen by src_ip, uri_path, uri_query, status| eval first_seen=strftime(first_seen, "%Y-%m-%d %H:%M:%S"), last_seen=strftime(last_seen, "%Y-%m-%d %H:%M:%S")| sort - count6. Forensic Analysis & Incident Response Playbook
Section titled โ6. Forensic Analysis & Incident Response Playbookโ-
Network Containment & Ingress Filtering: Block ingress traffic to Apache OFBiz web ports (default 8080 HTTP, 8443 HTTPS) from unauthenticated external IP addresses. Route management access strictly through corporate VPNs.
-
Inspect ofbiz.log for Screen Loading Exceptions: Review
/opt/ofbiz/runtime/logs/ofbiz.logfor anomalous file-based screen loading events:Terminal window grep -Ei "ScreenFactory|mainDecoratorLocation|groovy|upload" /opt/ofbiz/runtime/logs/ofbiz.log*Identify requests attempting to load resources from
/tmp/or outside the standard OFBiz component classpath. -
Check for Staged XML Payloads & Web Shells: Examine temporary directories and webapp document roots for recently created files:
Terminal window find /tmp /var/tmp -name "*upload*" -mtime -3find /opt/ofbiz/framework /opt/ofbiz/applications -name "*.jsp" -o -name "*.groovy" -mtime -3 -
Audit Child Processes Spawned by Java: Execute process monitoring commands to verify whether the
ofbizdaemon process has spawned shell processes:Terminal window ps -ef --forest | grep -A 5 -i "ofbiz"Look for child processes like
sh,bash,curl,python, ornc. -
Review Database Connection Integrity: Inspect database audit logs (e.g., PostgreSQL
pg_log) to verify whether bulk queries were executed against tables such asUSER_LOGIN,PARTY, orPAYMENT_PREFaround the time of the incident.
7. Remediation & Mitigation Strategy
Section titled โ7. Remediation & Mitigation StrategyโOfficial Vendor Patch
Section titled โOfficial Vendor PatchโThe Apache Software Foundation resolved CVE-2026-83542 in Apache OFBiz 24.09.08. Administrators must upgrade immediately:
- Download: Upgrade to Apache OFBiz 24.09.08 via the official Apache OFBiz Download Page.
- Core Fix: The patch enforces strict validation on
mainDecoratorLocation, restricting resolution exclusively to trusted internal classpath resources and completely rejecting externalfile:,http:, or relative filesystem URIs.
Temporary Defense-in-Depth Mitigations
Section titled โTemporary Defense-in-Depth MitigationsโIf an immediate upgrade cannot be deployed:
- WAF Regex Rule: Deploy an edge Web Application Firewall rule inspecting all URI query parameters and multipart request bodies for the pattern
mainDecoratorLocation=(file|http|https|/tmp). - Restrict Multipart Handlers: Disable public unauthenticated access to the
/sfa/control/editPortalPageColumnWidthroute at the reverse proxy layer (e.g., Nginx, Apache HTTP Server).