CVE-2020-36721

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

MEDIUM

6.5

CVSS Score

Published: June 7, 2023 at 01:51 AM UTC

Updated: June 17, 2026 at 03:16 AM UTC

18 products affected across 5 vendorsActivelloNewsMagAllegiant

Using Newspaper X by silkalns?

Get instant alerts when new vulnerabilities affect Newspaper X - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM6.5

Exploit prediction

EPSS 1.0%

SSVC

No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Activello · Colorlib

95%

v < 1.4.2

Affected range stops below 1.4.2, so it looks safe — our inference, not a vendor statement

Bonkers · Colorlib

95%

v < 1.0.6

Affected range stops below 1.0.6, so it looks safe — our inference, not a vendor statement

Illdy · Colorlib

95%

v < 2.1.7

Affected range stops below 2.1.7, so it looks safe — our inference, not a vendor statement

Newspaper X · Colorlib

95%

v < 1.3.2

Affected range stops below 1.3.2, so it looks safe — our inference, not a vendor statement

Pixova Lite · Colorlib

95%

v < 2.0.7

Affected range stops below 2.0.7, so it looks safe — our inference, not a vendor statement

Shapely · Colorlib

95%

v < 1.2.9

Affected range stops below 1.2.9, so it looks safe — our inference, not a vendor statement

Affluent · Cpothemes

95%

v < 1.1.2

Affected range stops below 1.1.2, so it looks safe — our inference, not a vendor statement

Allegiant · Cpothemes

95%

v < 1.2.6

Affected range stops below 1.2.6, so it looks safe — our inference, not a vendor statement

Brilliance · Cpothemes

95%

v < 1.3.0

Affected range stops below 1.3.0, so it looks safe — our inference, not a vendor statement

Transcend · Cpothemes

95%

v < 1.2.0

Affected range stops below 1.2.0, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

References (5)

ExploitThird Party Advisory

Source: [email protected]

https://blog.nintechnet.com/unauthenticated-function-injection-vulnerability-fixed-in-15-wordpress-themes/

Product

Source: [email protected]

https://wordpress.org/themes/activello/

Product

Source: [email protected]

https://wordpress.org/themes/brilliance/

Product

Source: [email protected]

https://wordpress.org/themes/newspaper-x/

Third Party Advisory

Source: [email protected]

https://www.wordfence.com/threat-intel/vulnerabilities/id/a9e4e989-8e55-4ea7-8f42-9f67cfab1168?source=cve

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

6.5MEDIUMWordfence

Vector?

Quick Info

StatusMODIFIED

CWE

CWE-862CWE-284

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card