Skip to content
Fencer Intel
high 7.5

CVE-2026-45441 json

WordPress WpEvently plugin <= 5.3.3 - Other Vulnerability Type vulnerability

published 4mo ago modified 14d ago also EUVD-2026-36842

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 17%
public exploits
0
none known

Summary

Unauthenticated Other Vulnerability Type in WpEvently <= 5.3.3 versions.

Patch / fix

  • Magepeople inc. WpEvently 5.3.4

Is CVE-2026-45441 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

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
4mo ago

Exploit prediction

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

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected products

  • Magepeople inc. WpEvently

Classification

Weakness
  • CWE-1284 Improper Validation of Specified Quantity in Input
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.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.