LatepointWordPress extension
CVE-2024-8911
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe LatePoint WordPress plugin before version 5.0.12 contains a critical SQL injection vulnerability that allows unauthenticated attackers to change arbitrary user passwords. The flaw stems from insufficient input sanitization on a user-supplied parameter combined with improper SQL query preparation, enabling direct manipulation of the database to modify password hashes for any WordPress user when the 'Use WordPress users as customers' setting is enabled.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
LatepointWordPress extension
< 5.0.12CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify LatePoint plugin is installedCheck the WordPress plugins directory or admin panel for the LatePoint plugin installation statusAffected if LatePoint plugin is present on the WordPress site
-
Determine installed LatePoint versionView the plugin file header (typically in /wp-content/plugins/latepoint/class-latepoint.php or through WordPress admin > Plugins > LatePoint) to find the version numberAffected if The installed version is earlier than 5.0.12 (e.g., 5.0.11, 5.0.10, etc.)
-
Check if WordPress user integration is enabledNavigate to LatePoint settings in WordPress admin (LatePoint > Settings > General) and locate the 'Use WordPress users as customers' optionAffected if The 'Use WordPress users as customers' setting is enabled (checked/turned on)
A site is affected if LatePoint plugin version is below 5.0.12 AND the 'Use WordPress users as customers' setting is enabled, allowing unauthenticated SQL injection leading to arbitrary WordPress user password modification.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped5.0.12
Update LatePoint to version 5.0.12 or later to remediate the SQL injection. If immediate updating is not possible, verify that the 'Use WordPress users as customers' setting is disabled (the default) to prevent WordPress user takeover, though customer table passwords may still be modifiable.
5.0.12
- 1. Create a complete backup of the WordPress site database and files
- 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- 3. Find the LatePoint plugin in the list
- 4. Click 'Update now' to update to the latest version (5.0.12 or later)
- 5. Alternatively, manually upload LatePoint version 5.0.12 or higher from wordpress.org/plugins
- 6. After updating, verify the plugin version shows 5.0.12 or later in the plugins list
- 7. If the 'Use WordPress users as customers' setting was previously enabled, audit all administrator-level user accounts for unauthorized changes and reset passwords as needed
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Latepoint
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-8911 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-8911 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data