WorkreapWordPress extension · Amentotech
CVE-2024-13446
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 Workreap plugin for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 3.2.5. This is due to the plugin not properly validating a user's identity prior to (1) performing a social auto-login or (2) updating their profile details (e.g. password). This makes it possible for unauthenticated attackers to (1) login as an arbitrary user if their email address is known or (2) change an arbitrary user's password, including administrators, and leverage that to gain access to their account. NOTE: This vulnerability was partially fixed in version 3.2.5.
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 Workreap WordPress plugin fails to validate user identity before performing social auto-login or updating profile details including passwords. Unauthenticated attackers can either login as any user by knowing their email address, or directly change any user's password including administrator accounts, enabling complete account takeover and privilege escalation.
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
WorkreapWordPress extension
< 3.2.6CVSS 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 Workreap plugin is installedCheck the WordPress plugins directory for the Workreap plugin folder (typically wp-content/plugins/workreap/) or list installed plugins via WP admin or wp-cli command: wp plugin list --name=workreapAffected if The plugin folder exists in the plugins directory and the plugin is active
-
Determine installed Workreap versionRead the plugin header from the main Workreap PHP file (usually workreap.php) to find the Version field, or run: wp plugin get workreap --field=versionAffected if The version number is less than 3.2.6 (for example: 3.2.5, 3.2.0, etc.)
-
Check if social login feature is enabledInspect the WordPress database options table for workreap_social_login settings, or check the plugin settings in WP admin under Workreap > Settings > Social LoginAffected if Social login is enabled and configured with any provider (Google, Facebook, LinkedIn, etc.)
-
Verify profile update endpoint is accessibleTest access to profile update endpoints without authentication by inspecting network requests or checking for AJAX actions related to profile update (such as workreap_update_profile or workreap_password_reset) in the plugin PHP files or by reviewing accessible AJAX hooksAffected if The profile update or password change AJAX actions are accessible to unauthenticated users (no auth check before processing)
-
Review access logs for suspicious activityCheck web server access logs (Apache/Nginx) for POST requests to /wp-admin/admin-ajax.php with workreap actions from unauthenticated IP addresses, particularly profile update or password reset actionsAffected if Unauthenticated requests were made to vulnerable Workreap AJAX endpoints, especially password change or profile update actions
If the Workreap plugin version is below 3.2.6 and the plugin is active on the WordPress site, the environment is affected by this authentication bypass vulnerability allowing account takeover.
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 · scoped3.2.6
Update Workreap to the latest version beyond 3.2.5 to address the incomplete fix, or disable and remove the plugin until a patched version is available. Consider implementing WAF rules to block the vulnerable profile update and social login endpoints as a temporary measure.
Workreap 3.2.6
- Navigate to WordPress admin dashboard > Plugins > Installed Plugins
- Find Workreap plugin and click 'Update now' to upgrade to version 3.2.6 or later
- Verify the updated version number in the Plugins list after updating
- As a security precaution, consider forcing password resets for all administrator accounts and users who may have been affected
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Workreap
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13446 — 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-13446 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