dbcve.org
Wpforo ForumWordPress extension · Gvectors

CVE-2026-28558

MEDIUM · 5.4 CVSS v3.1 Published 2026-02-28
Fix available
A fix is available. Upgrade to 2.4.16 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 a stored cross-site scripting vulnerability that allows authenticated subscribers to upload SVG files as profile avatars through the avatar upload functionality. Attackers upload a crafted SVG containing CSS injection or JavaScript event handlers that execute in the browsers of any user who views the attacker's profile page.

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

wpForo Forum 2.4.14 suffers from a stored cross-site scripting vulnerability via the avatar upload functionality. Authenticated subscribers can upload crafted SVG files containing JavaScript event handlers or CSS injection that execute in the browsers of any user who views the attacker's profile page.

MitigationImplement strict file type validation to block SVG uploads for avatars, or sanitize SVG content to remove all scriptable elements, event handlers, and potentially dangerous CSS before storage and serving.

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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. Confirm wpForo Forum installation and version
    Navigate to WordPress admin > Plugins and locate wpForo Forum, or check the version via FTP in /wp-content/plugins/wpforo/wpf-includes/version.php
    Affected if wpForo Forum version is 2.4.0 through 2.4.15 inclusive
  2. Verify avatar upload functionality is enabled
    Go to wpForo Forum settings > Profiles > Avatar Settings and check if avatar uploads are allowed for user roles
    Affected if Avatar upload is enabled for any user role, especially subscribers
  3. Check if subscriber role can upload avatars
    Navigate to wpForo > Settings > Members > Memberkit and review role capabilities, or inspect WordPress user roles to confirm subscribers have upload_avatar capability
    Affected if Subscriber or any low-privilege role has permission to upload avatars
  4. Inspect uploaded avatar files for SVG content
    Access /wp-content/uploads/wpforo/ via FTP or file manager, examine avatar image files for .svg extension with embedded script tags, event handlers (onclick, onload, etc.), or javascript: URLs
    Affected if SVG files exist in the avatar uploads directory containing script elements or event handler attributes
  5. Review profile pages for unsanitized SVG rendering
    View a user profile page where an avatar is displayed, inspect the page source to see if SVG files are served with proper Content-Type headers or are being sanitized
    Affected if SVG avatars are served directly without sanitization and browser renders them as XML/SVG content

You are affected if wpForo Forum version is between 2.4.0 and 2.4.15 and avatar upload is enabled for subscriber or other user roles.

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

Implement strict file type validation to block SVG uploads for avatars, or sanitize SVG content to remove all scriptable elements, event handlers, and potentially dangerous CSS before storage and serving.

Recommended fix High confidence

wpForo Forum version 2.4.16 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate wpForo Forum in the plugin list
  4. Check the current installed version (ensure it is < 2.4.16)
  5. Click 'Update now' if an update to version 2.4.16 or later is available
  6. Alternatively, download wpForo Forum 2.4.16 or latest version from wordpress.org
  7. Deactivate and delete the current wpForo Forum plugin
  8. Upload and install the new version

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
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28558 — 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-28558 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