Skip to content
Fencer Intel
medium 6.8

CVE-2020-23522 json

Pixelimity 1.0 has cross-site request forgery via the admin/setting.php data [Password] parameter.

published 5y ago modified 4mo ago also EUVD-2020-16266

cvss
6.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.0%
EPSS 2.0% chance of exploitation in 30 days, percentile 81%
public exploits
1
Exploit-DB

Summary

Pixelimity 1.0 has cross-site request forgery via the admin/setting.php data [Password] parameter.

Is CVE-2020-23522 in your stack? 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

Timeline

  1. Published
  2. First public exploit (EDB-49519)

Exploit prediction

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

Exploits and checks

  • EDB-49519 Pixelimity 1.0 - 'password' Cross-Site Request Forgery webapps, 2021-02-03
  • github.com https://github.com/pixelimity/pixelimity/issues/20 referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/161276/Pixelimity-1.0-Cross-Site-Request-Forgery.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness
  • CWE-352 Cross-Site Request Forgery

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.