WordPress security changelog
HIGH CVE-2021-39321 Modified

Sassy Social Share: Code execution

Sassy Social Share is affected by code execution. Exposure depends on how the affected operation is made reachable by the site. Successful exploitation can run attacker-controlled code in the WordPress hosting account.

CVE / CNA score 8.8 CVSS 3.1 · security@wordfence.com
NVD score 6.5 CVSS 2.0 · nvd@nist.gov
Component
Sassy Social Share
Plugin slug
sassy-social-share
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Oct 21, 2021
Weakness
CWE-502 — Deserialization of Untrusted Data
CWE-863 — Incorrect Authorization

This CVE was published Oct 21, 2021 and is one of 11 known issues for this plugin.

Update, patch or deactivate.

Update Sassy Social Share to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Technical description

Version 3.3.23 of the Sassy Social Share WordPress plugin is vulnerable to PHP Object Injection via the wp_ajax_heateor_sss_import_config AJAX action due to deserialization of unvalidated user supplied inputs via the import_config function found in the ~/admin/class-sassy-social-share-admin.php file. This can be exploited by underprivileged authenticated users due to a missing capability check on the import_config function.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

NVD vector: AV:N/AC:L/Au:S/C:P/I:P/A:P

Primary and upstream sources