sales@hackhalt.com

Home / Threats / CVE-2026-80514

wpForo Forum - Security Vulnerability (CVE-2026-80514)

CVE-2026-80514

The wpForo Forum WordPress plugin from 3.0.0 before 3.1.6 does not verify the source of client-supplied IP address headers before using them to key its per-visitor rate limit on paid AI requests, allowing unauthenticated attackers to bypass the limit by spoofing the header and exhaust the site owner's metered AI credits.

CVE-2026-80514

MEDIUM CVSS 5.3 Published 2026-09-25 Updated 2026-09-25
AI Risk Elevated (60/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P3 Priority
Severity Band MEDIUM
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Affected Components 2
Reference Links 1
AI Risk Engine Elevated (60/100)
Exploitability High
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2026-09-25 CVE published and first recorded in the threat feed.
  2. 2026-09-25 Record updated with latest vulnerability metadata.
  3. 2026-10-01 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 46 days ago

AI enriched 46 days ago (2026-10-01 15:55 UTC)

Technical Summary

The wpForo Forum WordPress plugin from 3.0.0 before 3.1.6 does not verify the source of client-supplied IP address headers before using them to key its per-visitor rate limit on paid AI requests, allowing unauthenticated attackers to bypass the limit by spoofing the header and exhaust the site owner's metered AI credits.

Potential Impact

Severity is MEDIUM (CVSS 5.3). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as High based on remote code execution potential, low-bar exploit prerequisites.

Primary risk drivers: remote code execution potential, low-bar exploit prerequisites

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 60/100 (Elevated, High) with priority P3 Priority. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

from 3 PLUGIN · from-3 Affected: >= 3.0.0, < 3.1.6 Fixed in: 3.1.6
wpForo Forum PLUGIN · wpforo-forum Affected: >= 3.0.0, < 3.1.6 Fixed in: 3.1.6

References

What to do about this

Patch promptly The consequence is significant even where an attacker needs a foothold first.

Fix it

Update wpForo Forum to 3.1.6 or later.

That is the complete fix. Everything below is what protects you in the meantime.

No Hack Halt control meaningfully contains this one — updating is the remedy. We would rather say so than sell you something that will not help.

Start free

Not sure if you are affected?

Scan your site to see whether it runs wpForo Forum, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?

You are affected if your site runs wpForo Forum. Versions below 3.1.6 are vulnerable; that release and later are not. No account is needed to exploit this, so a public site is reachable by anyone.

How do I fix it?

Update wpForo Forum to version 3.1.6 or later. That is the complete fix.