LiveActive security incident?Get immediate response
CVE Record

CVE-2025-69101: WordPress Workreap Core plugin <= 3.4.1 - Broken Authentication vulnerability

Authentication Bypass Using an Alternate Path or Channel vulnerability in AmentoTech Workreap Core workreap_core allows Authentication Abuse.This issue affects Workreap Core: from n/a through <= 3.4.1.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2025-69101 is a critical authentication bypass in the WordPress Workreap Core plugin. A remote unauthenticated attacker may be able to abuse an alternate authentication path, creating account takeover risk. Organizations running Workreap-based WordPress sites should treat this as urgent, especially for internet-facing sites.

Executive priority

High priority. The issue combines critical severity, unauthenticated network exposure, and potential account takeover impact. If Workreap Core is used on public sites, assign immediate ownership for inventory, vendor guidance review, and remediation planning.

Technical view

The CVE describes CWE-288, Authentication Bypass Using an Alternate Path or Channel, affecting AmentoTech Workreap Core through version 3.4.1. CVSS 3.1 is 9.8: network exploitable, low complexity, no privileges, no user interaction, with high confidentiality, integrity, and availability impact.

Likely exposure

Internet-facing WordPress sites using AmentoTech Workreap Core versions up to and including 3.4.1 are the likely exposure set. The bundle does not identify other affected products.

Exploitation context

The CVSS vector indicates unauthenticated remote exploitation is plausible without user interaction. The CVE is not listed as KEV in the provided bundle, and no cited source confirms active exploitation.

Researcher notes

Evidence is limited to the CVE record and Patchstack reference. The source bundle states affected through 3.4.1, while the Patchstack URL text references 3.4.0. Treat 3.4.1 and earlier as in scope until vendor guidance clarifies.

Mitigation direction

  • Inventory WordPress sites for the Workreap Core plugin.
  • Identify any Workreap Core installation at version 3.4.1 or earlier.
  • Check AmentoTech and Patchstack guidance for a fixed version or official mitigation.
  • Apply vendor-supported updates as soon as available and tested.
  • If no fix is available, consider disabling the plugin after business impact review.

Validation and detection

  • Confirm plugin name, slug, and version from WordPress administration or asset inventory.
  • Prioritize externally reachable WordPress sites using Workreap Core.
  • Review recent WordPress user, admin, and authentication activity for anomalies.
  • Check whether emergency controls changed plugin behavior or site functionality.
  • Track vendor advisories until a fixed version or mitigation is confirmed.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-288: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-69101 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2025-69101Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AmentoTechWorkreap Coreworkreap_core, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-288 · source CWE mapping

Authentication Bypass Using an Alternate Path or Channel

Authentication Bypass Using an Alternate Path or Channel represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.