CVE-2025-4973

Workreap <= 3.3.1 - Authentication Bypass via 'workreap_verify_user_account'

2025-06-11 16:31
Foxyyy

Strategic Overview

Status
Patched in 3.3.2
Affected Plugin
Workreap
Affected Version
<= 3.3.1
CVSS
9.8Critical
Weakness type
CWE-288 · Authentication Bypass Using an Alternate Path or Channel
CVE
CVE-2025-4973
View all Workreap vulnerabilities

At a glance

CVE-2025-4973 is a critical-severity Authentication Bypass Using an Alternate Path or Channel vulnerability in the Workreap WordPress plugin, affecting versions <= 3.3.1. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.3.2; sites on affected versions should update now. Disclosed June 2025, reported by Foxyyy.

Vulnerability Overview

The Workreap plugin for WordPress, used by the Workreap - Freelance Marketplace WordPress Theme, is vulnerable to authentication bypass in all versions up to, and including, 3.3.1. This is due to the plugin not properly verifying a user's identity prior to logging them in when verifying an account with an email address. This makes it possible for unauthenticated attackers to log in as registered users, including administrators, if they know user's email address. This is only exploitable fi the user's confirmation_key has not already been set by the plugin.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-288: Authentication Bypass Using an Alternate Path or Channel

Reaching this weakness in Workreap <= 3.3.1 takes a caller who can reach the endpoint. Authentication bypass through an alternate path means the application has a second route to a protected action that skips the checks the primary route performs.

The protection on the main path becomes irrelevant, because the attacker simply uses the route that never asks. For Workreap the fix is 3.3.2: builds <= 3.3.1 are affected, anything from 3.3.2 onward is not.

Remediation

Update to version 3.3.2, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Workreap 3.3.2 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-4973https://www.wordfence.com/threat-intel/vulnerabilities/id/8e7693a3-642a-4eff-902c-d29a3c12deb0https://nvd.nist.gov/vuln/detail/CVE-2025-4973

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C