Skip to content
Fencer Intel
critical 9.8

CVE-2020-28032 in the critical feed json

WordPress before 5.5.2 mishandles deserialization requests in wp-includes/Requests/Utility/FilteredIterator.php.

published 6y ago modified 2mo ago also BIT-wordpress-2020-28032 , BIT-wordpress-multisite-2020-28032 , EUVD-2020-20523

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
15.7%
EPSS 15.7% chance of exploitation in 30 days, percentile 96%
public exploits
0
none known

Summary

WordPress before 5.5.2 mishandles deserialization requests in wp-includes/Requests/Utility/FilteredIterator.php.

Patch / fix

  • bitnami wordpress 5.5.2
  • bitnami wordpress-multisite 5.5.2
  • wordpress wordpress 5.5.2
  • wordpress Debian 14, Debian 13, Debian 12 5.5.3+dfsg1-1

debian advisories DEBIAN-CVE-2020-28032

  • wordpress Arch Linux 5.5.3-1

arch linux advisories AVG-1257

Is CVE-2020-28032 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-28032 updated cvss 9.8

wordpress: hardening deserialization requests

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

15.70% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
OSV 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
bitnami wordpress
<5.5.2
5.5.2
bitnami wordpress-multisite
<5.5.2
5.5.2

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data
Technology feeds

References

Sources

Fencer Intel 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.