No. Junglewise Threat Intelligence has no report of CVE-2020-28735 being exploited in the wild.
How severe is CVE-2020-28735?
Low severity, with a CVSS score of 3.1, published 2 July 2026.
Which products and versions are affected?
plone (PyPI) ECOSYSTEM:introduced=0,fixed=5.2.3; plone-app-theming (PyPI) ECOSYSTEM:introduced=0,fixed=4.1.6; plone-supermodel (PyPI) ECOSYSTEM:introduced=0,fixed=1.6.3; plone.app.dexterity (PyPI) ECOSYSTEM:introduced=0,fixed=2.6.8; and 1 more.
Is there a fix for CVE-2020-28735?
Yes. plone (PyPI): upgrade to 5.2.3 or later; plone-app-theming (PyPI): upgrade to 4.1.6 or later; plone-supermodel (PyPI): upgrade to 1.6.3 or later; plone.app.dexterity (PyPI): upgrade to 2.6.8 or later; plone.app.event (PyPI): upgrade to 3.2.10 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2020-28735?
Check whether you run plone (PyPI), plone-app-theming (PyPI), plone-supermodel (PyPI) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
plone (PyPI): upgrade to 5.2.3 or later
pip install "plone>=5.2.3"
plone-app-theming (PyPI): upgrade to 4.1.6 or later
pip install "plone-app-theming>=4.1.6"
plone-supermodel (PyPI): upgrade to 1.6.3 or later
pip install "plone-supermodel>=1.6.3"
plone.app.dexterity (PyPI): upgrade to 2.6.8 or later
pip install "plone.app.dexterity>=2.6.8"
plone.app.event (PyPI): upgrade to 3.2.10 or later