dbcve.org
Support BoardWordPress extension · Schiocco

CVE-2025-4828

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-09
Fix available
A fix is available. Upgrade to 3.8.1 or later.
See remediation →
100/100
Remediation priority · Urgent
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
The Support Board plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the sb_file_delete function in all versions up to, and including, 3.8.0. This makes it possible for attackers to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). An attacker can leverage CVE-2025-4855 vulnerability to exploit this vulnerability unauthenticated.

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

The Support Board WordPress plugin contains an arbitrary file deletion vulnerability in the sb_file_delete function due to insufficient file path validation. Attackers can supply path traversal sequences (e.g., ../../wp-config.php) to delete any file on the server accessible to the web server process. When chained with CVE-2025-4855 for unauthenticated access, this allows unauthenticated attackers to achieve remote code execution by deleting critical files like wp-config.php.

MitigationUpdate the Support Board plugin to version 3.8.1 or later if available, or implement server-side validation in sb_file_delete to ensure the requested file path resolves within an allowed directory and reject path traversal sequences.

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
Support BoardWordPress extension
Affected:< 3.8.1

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
High
Integrity
High
Availability
High

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

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 WordPress installation
    Check for the presence of wp-config.php in the web root directory, or look for WordPress-specific files and directories such as /wp-admin/ or /wp-includes/.
    Affected if The server is running WordPress and may be hosting the Support Board plugin.
  2. Confirm Support Board plugin is installed
    Navigate to /wp-content/plugins/ directory and check for a folder named 'support-board' or 'sb'. Alternatively, check the WordPress admin plugins list if admin access is available.
    Affected if The Support Board plugin files exist in the WordPress plugins directory.
  3. Determine installed Support Board version
    If admin access is available, go to Plugins > Support Board and view the version number. Alternatively, check the main plugin file (e.g., support-board/index.php or sb.php) for a version comment or constant definition.
    Affected if The installed version is lower than 3.8.1 (e.g., 3.8.0, 3.7.x, or earlier).
  4. Check for vulnerable sb_file_delete function
    Inspect the plugin source code for the function named 'sb_file_delete' or 'file_delete'. Look in files such as /wp-content/plugins/support-board/includes/functions.php or similar include files.
    Affected if The sb_file_delete function exists in the plugin code without proper path validation.
  5. Verify exposure of delete functionality
    Review the plugin's AJAX endpoints or direct function calls that invoke sb_file_delete. Check if the endpoint is accessible without authentication by examining the 'nopriv' capability in WordPress AJAX hooks or the plugin's router configuration.
    Affected if The file delete functionality is exposed via a publicly accessible URL or AJAX endpoint without requiring authentication.

A user is affected if they have the Support Board plugin installed with a version lower than 3.8.1, and the sb_file_delete function is accessible (especially without authentication when chained with CVE-2025-4855), allowing path traversal-based arbitrary file deletion.

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 3.8.1 or later
Fixed in 3.8.1
Interim mitigation

Update the Support Board plugin to version 3.8.1 or later if available, or implement server-side validation in sb_file_delete to ensure the requested file path resolves within an allowed directory and reject path traversal sequences.

Recommended fix High confidence

Support Board 3.8.1

  1. Create a complete backup of the WordPress site (database and all files)
  2. Navigate to the WordPress admin dashboard > Plugins > Installed Plugins
  3. Find the Support Board plugin and click 'Update now' (or upload version 3.8.1 manually if automatic update is not available)
  4. Verify the plugin version shows 3.8.1 after the update completes
  5. Confirm the plugin functionality is working normally

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

Fix this in Support Board Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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