HarborGuardharborguardDatabase
Back to search
CRITICALCVE-2026-42682Published Modified CNA Patchstack

CVE-2026-42682: WordPress wpForo Forum plugin <= 3.0.6 - Broken Access Control vulnerability

Missing Authorization vulnerability in Tomdever wpForo Forum allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects wpForo Forum: from n/a through 3.0.6.

Metrics

CVSS v3.1
9.1
Severity
CRITICAL
Fixed in
Affected Products
1

Get notified

Email me when this CVE is updated: new fix versions, severity changes, or any record change.

HarborGuard Analysis

Synopsis

This is a broken access control vulnerability in the wpForo Forum WordPress plugin, affecting all versions through 3.0.6. The flaw is reachable over the network and requires no authentication, meaning any anonymous user on the internet can trigger it. Successful exploitation allows an attacker to tamper with forum data and disrupt availability of the affected service. No fix version has been published yet; HarborGuard tracks the advisory and will surface a patched-image rebuild the moment upstream ships a remediated release.

HarborGuard Coverage

Detection

Detection for CVE-2026-42682 is available across every HarborGuard environment: the CVE is ingested from upstream feeds, including the Patchstack advisory, within minutes of publication and matched against customer images in connected registries and CI pipelines. This matching covers custom-built images that bundle the wpForo Forum plugin alongside WordPress.

Available
Triage

HarborGuard is capable of scoring this finding at its published CVSS 3.1 rating of 9.1 (Critical) and weighting it against each environment's compliance policy to determine urgency. Findings are routed to the appropriate team inbox within each customer organization based on configured ownership rules.

Available
Patch

Because no fix version has been published, HarborGuard re-checks the Patchstack advisory and upstream plugin repository on every ingest cycle. A patched-image rebuild will become available automatically the moment a remediated version of wpForo Forum is released, and customers with auto-remediation enabled will receive a rebuild, regression-test run, and a PR opened against affected workloads without manual intervention.

Pending upstream

Exploit Conditions

  • Network reachabilityRequired

    The vulnerable endpoint is exposed over the network, so an attacker must be able to reach the WordPress installation via HTTP/HTTPS from any internet-connected location.

  • AuthenticationNot required

    No account or session token is needed; the flaw is exploitable by an anonymous, unauthenticated request.

  • Victim interactionNot required

    The attacker does not need to trick any user into taking an action; the exploit is executed entirely by the attacker.

  • Attack complexityDetail

    Attack complexity is low, meaning the exploit is reliable and imposes no special conditions such as race conditions or specific memory layout requirements.

Blast Radius

  • An attacker can modify forum content, settings, or user-controlled data without authorization, bypassing role and permission checks.
  • An attacker can disrupt availability of the forum service, causing denial of service to legitimate users.
  • Because integrity and availability are both rated High and confidentiality is unaffected, stored data is at risk of tampering or deletion but not direct read-based disclosure through this vector alone.

How HarborGuard Handles This

Available on HarborGuard: because no upstream fix exists for CVE-2026-42682 as of the publication date, the immediate capability offered is continuous advisory monitoring paired with compensating-control guidance. Teams can reduce exposure by applying network-policy rules that restrict public access to the WordPress admin and forum API endpoints, enabling egress filtering on containers running this plugin, and disabling wpForo features that are not actively used via WordPress configuration until a patch is available. HarborGuard re-evaluates the advisory on every ingest cycle; where compliance policy permits auto-remediation, a rebuilt image and pull request against affected workloads will be generated automatically once Tomdever publishes a patched release. For environments that cannot wait, manual pinning of the affected image to a network-isolated policy zone is configurable directly from the HarborGuard findings dashboard.

See how HarborGuard automates this
Affected packages
  • Tomdever / wpForo Forum
    ≤ 3.0.6
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
References