Skip to content
Fencer Vulns
medium 6.1

CVE-2020-9496 json

XML-RPC request are vulnerable to unsafe deserialization and Cross-Site Scripting issues in Apache OFBiz 17.12.03

published 2020-07-15 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-30302

cvss
6.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
98.9%
EPSS 98.9% chance of exploitation in 30 days, percentile 99.9%
public exploits
2
Metasploit, Exploit-DB, plus a Nuclei check

Summary

XML-RPC request are vulnerable to unsafe deserialization and Cross-Site Scripting issues in Apache OFBiz 17.12.03

Timeline

  1. First public exploit (Metasploit exploit/linux/http/apache_ofbiz_deserialization)
  2. Published

Exploit prediction

98.93% chance of exploitation in the next 30 days, higher than 99.9% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • Metasploit exploit/linux/http/apache_ofbiz_deserialization Apache OFBiz XML-RPC Java Deserialization metasploit exploit, excellent rank, 2020-07-13
  • EDB-50178 ApacheOfBiz 17.12.01 - Remote Command Execution (RCE) webapps, 2021-08-04
  • Nuclei template Apache OFBiz 17.12.03 - Cross-Site Scripting nuclei detection template
  • packetstormsecurity.com http://packetstormsecurity.com/files/158887/Apache-OFBiz-XML-RPC-Java-Deserialization.html referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/161769/Apache-OFBiz-XML-RPC-Java-Deserialization.html referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/163730/Apache-OfBiz-17.12.01-Remote-Command-Execution.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N

Affected products

  • n/a Apache OFBiz

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation
  • CWE-502 Deserialization of Untrusted Data

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.