Skip to content
Fencer Intel
medium 4.3

CVE-2020-28040 json

WordPress before 5.5.2 allows CSRF attacks that change a theme's background image.

published 6y ago modified 2mo ago also BIT-wordpress-2020-28040 , BIT-wordpress-multisite-2020-28040 , EUVD-2020-20531

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

Summary

WordPress before 5.5.2 allows CSRF attacks that change a theme's background image.

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-28040

  • wordpress Arch Linux 5.5.3-1

arch linux advisories AVG-1257

Is CVE-2020-28040 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-28040 updated cvss 4.3

wordpress: CSRF attacks that change a theme's background image

  • 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

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

CVSS scores

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

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-352 Cross-Site Request Forgery
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.