dbcve.org
Wpforo ForumWordPress extension · Gvectors

CVE-2026-28559

MEDIUM · 5.3 CVSS v3.1 Published 2026-02-28
Fix available
A fix is available. Upgrade to 2.4.16 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
wpForo Forum 2.4.14 contains an information disclosure vulnerability that allows unauthenticated users to retrieve private and unapproved forum topics via the global RSS feed endpoint. Attackers request the RSS feed without a forum ID parameter, bypassing the privacy and status WHERE clauses that are only applied when a specific forum ID is present in the query.

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 · moderate confidence

wpForo Forum 2.4.14 has an information disclosure vulnerability in its global RSS feed endpoint. When the RSS feed is accessed without a forum ID parameter, the SQL query skips the WHERE clauses that enforce privacy settings and topic approval status, allowing unauthenticated users to view private and unapproved forum topics.

MitigationFix the RSS feed endpoint to always apply privacy and approval status WHERE clauses regardless of whether a forum ID parameter is provided, or restrict unauthenticated access to the global RSS feed.

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
Wpforo ForumWordPress extension
Affected:>= 2.4.0, < 2.4.16

CVSS 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
Low
Integrity
None
Availability
None

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify wpForo Forum plugin is installed
    Check your WordPress plugins page or inspect the wp-content/plugins/wpforo folder for the plugin
    Affected if wpForo Forum plugin is not present on the system
  2. Confirm installed version is within affected range
    Check the plugin version in WordPress admin under Plugins > Installed Plugins, or read the main plugin file header
    Affected if Version is 2.4.0 through 2.4.15 (anything >= 2.4.0 but < 2.4.16)
  3. Access the global RSS feed endpoint without authentication
    Navigate to the wpForo RSS feed URL without providing a forum ID parameter, typically at /?wpforo=feed or /feed/ depending on configuration, without logging in
    Affected if The RSS feed loads and displays content without requiring authentication
  4. Verify privacy bypass by checking for private topic content
    Examine the RSS feed output for topics from forums marked as private or restricted, and look for content that should not be visible to unauthenticated users
    Affected if Private forum topics or unapproved topics appear in the unauthenticated RSS feed output

You are affected if wpForo Forum version is >= 2.4.0 and < 2.4.16 AND the global RSS feed endpoint is accessible to unauthenticated users and displays private or unapproved content

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.4.16 or later
Fixed in 2.4.16
Interim mitigation

Fix the RSS feed endpoint to always apply privacy and approval status WHERE clauses regardless of whether a forum ID parameter is provided, or restrict unauthenticated access to the global RSS feed.

Recommended fix High confidence

wpForo Forum 2.4.16

  1. Backup your WordPress site and database before performing any updates
  2. Navigate to the WordPress admin dashboard
  3. Go to Plugins > Installed Plugins
  4. Locate wpForo Forum in the plugin list
  5. Check if an update is available (should show version 2.4.16 or higher)
  6. Click 'Update Now' to upgrade to the latest version
  7. Alternatively, manually download wpForo Forum 2.4.16 from wordpress.org and upload via Plugins > Add New > Upload Plugin
  8. After updating, verify the RSS feed now properly restricts private/unapproved topics based on the privacy and status checks

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wpforo Forum Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28559 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-28559 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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