Skip to content
Fencer Vulns
medium 6.5

CVE-2020-36721 json

Epsilon Framework Themes (Various Versions) - Unauthenticated Plugin Activation/Deactivation

published 2023-06-07 3 y ago modified 2026-06-17 4 mo ago also EUVD-2020-24163

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

Summary

The Brilliance <= 1.2.7, Activello <= 1.4.0, and Newspaper X <= 1.3.1 themes for WordPress are vulnerable to Plugin Activation/Deactivation. This is due to the 'activello_activate_plugin' and 'activello_deactivate_plugin' functions in the 'inc/welcome-screen/class-activello-welcome.php' file missing capability and security checks/nonces. This makes it possible for unauthenticated attackers to activate and deactivate arbitrary plugins installed on a vulnerable site.

Patch / fix

  • colorlib activello 1.4.2
  • colorlib bonkers 1.0.6
  • colorlib illdy 2.1.7
  • colorlib newspaper_x 1.3.2
  • colorlib pixova_lite 2.0.7
  • colorlib shapely 1.2.9
  • cpothemes affluent 1.1.2
  • cpothemes allegiant 1.2.6
  • cpothemes brilliance 1.3.0
  • cpothemes transcend 1.2.0
  • machothemes antreas 1.0.7
  • machothemes medzone_lite 1.2.6
  • machothemes newsmag 2.4.2
  • machothemes regina_lite 2.0.6

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
22 mo ago

Exploit prediction

0.97% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • blog.nintechnet.com https://blog.nintechnet.com/unauthenticated-function-injection-vulnerability-fixed-in-15-wordpress-themes/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Affected products

  • wpchill Brilliance
  • silkalns Newspaper X
  • silkalns Activello

Classification

Weakness
Technology feeds

References

Sources

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