Skip to content
Fencer Intel
medium 4.3

CVE-2022-0377 json

LearnPress < 4.1.5 - Arbitrary Image Renaming

published 4y ago modified 4mo ago also EUVD-2022-15528

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

Summary

Users of the LearnPress WordPress plugin before 4.1.5 can upload an image as a profile avatar after the registration. After this process the user crops and saves the image. Then a "POST" request that contains user supplied name of the image is sent to the server for renaming and cropping of the image. As a result of this request, the name of the user-supplied image is changed with a MD5 value. This process can be conducted only when type of the image is JPG or PNG. An attacker can use this vulnerability in order to rename an arbitrary image file. By doing this, they could destroy the design of the web site.

Patch / fix

  • Unknown LearnPress 4.1.5

Is CVE-2022-0377 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. First public exploit (EDB-50706)
  2. Published

Exploit prediction

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

Exploits and checks

  • EDB-50706 WordPress Plugin Learnpress 4.1.4.1 - Arbitrary Image Renaming webapps, 2022-02-02
  • wpscan.com https://wpscan.com/vulnerability/0d95ada6-53e3-4a80-a395-eacd7b090f26 referenced PoC, tagged "exploit" by a source, unverified
  • bozogullarindan.com https://bozogullarindan.com/en/2022/01/wordpress-learnpress-plugin-4.1.4.1-arbitrary-image-renaming/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Affected products

  • Unknown LearnPress

Classification

Weakness
  • CWE-327 Use of a Broken or Risky Cryptographic Algorithm
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.