dbcve.org
Support BoardWordPress extension · Schiocco

CVE-2025-4855

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 unauthorized access/modification/deletion of data due to use of hardcoded default secrets in the sb_encryption() function in all versions up to, and including, 3.8.0. This makes it possible for unauthenticated attackers to bypass authorization and execute arbitrary AJAX actions defined in the sb_ajax_execute() function. An attacker can use this vulnerability to exploit CVE-2025-4828 and various other functions 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 uses hardcoded default secrets in the sb_encryption() function, allowing unauthenticated attackers to bypass authentication and execute arbitrary AJAX actions through the sb_ajax_execute() function. This enablesChaining with CVE-2025-4828 and other functions for complete site compromise.

MitigationUpdate the Support Board plugin to version 3.8.1 or later to replace hardcoded secrets with dynamic encryption keys; if no update is available, remove the plugin immediately.

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 Support Board plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Support Board' or 'Schiocco Support Board'. Note the version number displayed.
    Affected if The plugin is installed and version is below 3.8.1
  2. Check plugin version via file inspection
    If WP admin access is unavailable, inspect the main plugin file (typically /wp-content/plugins/support-board/support-board.php or similar) and locate the 'Version' header comment.
    Affected if Version header shows a number less than 3.8.1
  3. Locate the sb_encryption function
    Search the plugin directory for the function definition 'function sb_encryption' - this is typically in include files under /inc/ folder. Open the file and inspect the function body.
    Affected if The function contains hardcoded string literals used as encryption keys (default/fixed secrets rather than dynamically generated values)
  4. Verify AJAX endpoint accessibility
    Check if the file containing sb_ajax_execute() is accessible via wp-admin/admin-ajax.php or direct URL access without authentication. Look for AJAX hooks registered with 'wp_ajax_nopriv_' allowing unauthenticated access.
    Affected if AJAX actions registered with 'wp_ajax_nopriv_' point to functions using sb_ajax_execute() or the vulnerable encryption logic

You are affected if the Support Board plugin is installed with a version below 3.8.1 and the plugin code contains hardcoded encryption secrets in the sb_encryption function accessible via unauthenticated AJAX endpoints.

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 to replace hardcoded secrets with dynamic encryption keys; if no update is available, remove the plugin immediately.

Recommended fix High confidence

Support Board version 3.8.1

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Support Board plugin in the list
  4. Update the plugin to version 3.8.1 or later
  5. Verify the update was successful by checking the plugin version

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

Fix this in Support Board Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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