Skip to main content
ExploitedNot in CISA KEV yetFix available

CVE-2011-3600

Exploitation confirmed. First attested on 2023-10-14 by GCVE · kevintel, GCVE · shadowserver.

  • Published2019-11-26
  • WeaknessCWE-611

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

The /webtools/control/xmlrpc endpoint in OFBiz XML-RPC event handler is exposed to External Entity Injection by passing DOCTYPE declarations with executable payloads that discloses the contents of files in the filesystem. In addition, it can also be used to probe for open network ports, and figure out from returned error messages whether a file exists or not. This affects OFBiz 16.11.01 to 16.11.04.

Timeline

dates in UTC
  1. 2019-11-2601:15CVE publishedNVD
  2. 2023-10-1414:56Listed as exploited by GCVEGCVE
  3. 2023-10-1414:56Exploitation first reportedGCVE

Observed activity

isMalicious corpus · updated 2026-11-03 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2011-3600?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2011-3600?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Apache ofbiz
BranchAffectedFixed in
16.11≥ 16.11.01, ≤ 16.11.04no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

  • CVE-2011-3600 Red Hat Product Security8 known affected

    XML-RPC SAX parser information exposure

    xmlrpc3-client as a component of Red Hat Enterprise Linux 6 · xmlrpc3-client-devel as a component of Red Hat Enterprise Linux 6 · xmlrpc3-common as a component of Red Hat Enterprise Linux 6 · +5 more

Full record on NVD

Fix

  1. No fix planned, says the vendor Red Hat Product Security CVE-2011-3600 · 8 productsWill not fix

Advisories and patches

Detection

read 2026-11-03 22:42 UTC
Nuclei template
available
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub
Metasploit modules
none listed
Metasploit Framework

Sources

  • GCVEexploitation2023-10-14
  • NVDCVSS 3.17.5read 2026-10-23
  • NVDCVSS 2.05read 2026-10-23
  • NVDweakness (CWE)CWE-611read 2026-10-23
  • FIRST EPSSEPSS score15.9 %read 2026-11-03
  • ProjectDiscoverydetectionread 2026-11-03

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Published
2019-11-26
Last Modified
2026-06-16
NVD status
Modified

Frequently asked questions

What is CVE-2011-3600?

The /webtools/control/xmlrpc endpoint in OFBiz XML-RPC event handler is exposed to External Entity Injection by passing DOCTYPE declarations with executable payloads that discloses the contents of files in the filesystem. In addition, it can also be used to probe for open network ports, and figure out from returned error messages whether a file exists or not. This affects OFBiz 16.11.01 to 16.11.04.

Is CVE-2011-3600 actively exploited?

Active exploitation of CVE-2011-3600 has not been confirmed. Its EPSS score was 15.9% on 2026-11-03, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2011-3600?

CVE-2011-3600 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record