CVE-2021-39317

A WordPress plugin and several WordPress themes developed by AccessPress Themes are vulnerable to malicious file uploads via the plugin_offline_installer AJAX action due to a missing capability check in the plugin_offline_installer_callback function found in the /demo-functions.php file or /welcome.php file of the affected products. The complete list of affected products and their versions are below: WordPress Plugin: AccessPress Demo Importer <=1.0.6 WordPress Themes: accesspress-basic <= 3.2.1 accesspress-lite <= 2.92 accesspress-mag <= 2.6.5 accesspress-parallax <= 4.5 accesspress-root <= 2.5 accesspress-store <= 2.4.9 agency-lite <= 1.1.6 arrival <= 1.4.2 bingle <= 1.0.4 bloger <= 1.2.6 brovy <= 1.3 construction-lite <= 1.2.5 doko <= 1.0.27 edict-lite <= 1.1.4 eightlaw-lite <= 2.1.5 eightmedi-lite <= 2.1.8 eight-sec <= 1.1.4 eightstore-lite <= 1.2.5 enlighten <= 1.3.5 fotography <= 2.4.0 opstore <= 1.4.3 parallaxsome <= 1.3.6 punte <= 1.1.2 revolve <= 1.3.1 ripple <= 1.2.0 sakala <= 1.0.4 scrollme <= 2.1.0 storevilla <= 1.4.1 swing-lite <= 1.1.9 the100 <= 1.1.2 the-launcher <= 1.3.2 the-monday <= 1.4.1 ultra-seven <= 1.2.8 uncode-lite <= 1.3.3 vmag <= 1.2.7 vmagazine-lite <= 1.3.5 vmagazine-news <= 1.0.5 wpparallax <= 2.0.6 wp-store <= 1.1.9 zigcy-baby <= 1.0.6 zigcy-cosmetics <= 1.0.5 zigcy-lite <= 2.0.9

Weakness

The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.

Affected Software

Name	Vendor	Start Version	End Version
Access_demo_importer	Accesspressthemes	*	1.0.7 (excluding)
Accesspress-lite	Accesspressthemes	*	2.92 (including)
Accesspress-mag	Accesspressthemes	*	2.6.5 (including)
Accesspress-parallax	Accesspressthemes	*	4.5 (including)
Accesspress-root	Accesspressthemes	*	2.5 (including)
Accesspress-store	Accesspressthemes	*	2.4.9 (including)
Accesspress_basic	Accesspressthemes	*	3.2.1 (including)
Agency-lite	Accesspressthemes	*	1.1.6 (including)
Arrival	Accesspressthemes	*	1.4.2 (including)
Bingle	Accesspressthemes	*	1.0.4 (including)
Bloger	Accesspressthemes	*	1.2.6 (including)
Brovy	Accesspressthemes	*	1.3 (including)
Construction-lite	Accesspressthemes	*	1.2.5 (including)
Doko	Accesspressthemes	*	1.0.27 (including)
Edict-lite	Accesspressthemes	*	1.1.4 (including)
Eight-sec	Accesspressthemes	*	1.1.4 (including)
Eightlaw-lite	Accesspressthemes	*	2.1.5 (including)
Eightmedi-lite	Accesspressthemes	*	2.1.8 (including)
Eightstore-lite	Accesspressthemes	*	1.2.5 (including)
Enlighten	Accesspressthemes	*	1.3.5 (including)
Fotography	Accesspressthemes	*	2.4.0 (including)
Opstore	Accesspressthemes	*	1.4.3 (including)
Parallaxsome	Accesspressthemes	*	1.3.6 (including)
Punte	Accesspressthemes	*	1.1.2 (including)
Revolve	Accesspressthemes	*	1.3.1 (including)
Ripple	Accesspressthemes	*	1.2.0 (including)
Sakala	Accesspressthemes	*	1.0.4 (including)
Scrollme	Accesspressthemes	*	2.1.0 (including)
Storevilla	Accesspressthemes	*	1.4.1 (including)
Swing-lite	Accesspressthemes	*	1.1.9 (including)
The-launcher	Accesspressthemes	*	1.3.2 (including)
The-monday	Accesspressthemes	*	1.4.1 (including)
The100	Accesspressthemes	*	1.1.2 (including)
Ultra-seven	Accesspressthemes	*	1.2.8 (including)
Uncode-lite	Accesspressthemes	*	1.3.3 (including)
Vmag	Accesspressthemes	*	1.2.7 (including)
Vmagazine-lite	Accesspressthemes	*	1.3.5 (including)
Vmagazine-news	Accesspressthemes	*	1.0.5 (including)
Wp-store	Accesspressthemes	*	1.1.9 (including)
Wpparallax	Accesspressthemes	*	2.0.6 (including)
Zigcy-baby	Accesspressthemes	*	1.0.6 (including)
Zigcy-cosmetics	Accesspressthemes	*	1.0.5 (including)
Zigcy-lite	Accesspressthemes	*	2.0.9 (including)

Potential Mitigations

Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page.
One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.

NVD	https://nvd.nist.gov/vuln/detail/CVE-2021-39317
CWE	https://cwe.mitre.org/data/definitions/285.html

Improper Authorization

Weakness

Affected Software

Potential Mitigations

References

CVE-2021-39317

Improper Authorization

Weakness

Affected Software

Potential Mitigations

Related Attack Patterns

References