CVE-2024-8911
LatePoint <= 5.0.11 - Unauthenticated Arbitrary User Password Change via SQL Injection
Record summary
CVE-2024-8911 has a selected CVSS score of 9.8 (critical); EIP currently links 1 Nuclei template.
Description
The LatePoint plugin for WordPress is vulnerable to Arbitrary User Password Change via SQL Injection in versions up to, and including, 5.0.11. This is due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to change user passwords and potentially take over administrator accounts. Note that changing a WordPress user's password is only possible if the "Use WordPress users as customers" setting is enabled, which is disabled by default. Without this setting enabled, only the passwords of plugin customers, which are stored and managed in a separate database table, can be modified.
Exploitation context
Known exploitation
- VulnCheck KEV
- Listed · Oct 8, 2024 · VulnCheck
- Reported exploitation
- Observed · VulnCheck
Available material
- Nuclei templates
- 1
CISA SSVC decision
CISA Coordinator · SSVC 2.0.3 · Evaluated Oct 9, 2024 · Source: CVE List
Affected products and versions
2| Product | Source | Version range | Status |
|---|---|---|---|
LatePoint PluginBrowse latepoint / LatePoint PluginDefault status: unaffected | CVE List | Through 5.0.11 | affected |
latepointBrowse latepoint / latepointDefault status: unknown | CVE List, VulnCheck | Through 5.0.11 | affected |
Nuclei templates
1ProjectDiscoveryCRITICALLatePoint <= 5.0.11 - SQL InjectionCVSS 9.8
The LatePoint plugin for WordPress is vulnerable to Arbitrary User Password Change via SQL Injection in versions up to, and including, 5.0.11. This is due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to change user passwords and potentially take over administrator accounts. Note that changing a WordPress user's password is only possible if the "Use WordPress users as customers" setting is enabled, which is disabled by default. Without this setting enabled, only the passwords of plugin customers, which are stored and managed in a separate database table, can be modified.
Source: ProjectDiscovery