dbcve.org
Support BoardWordPress extension · Schiocco

CVE-2026-4815

HIGH · 8.8 CVSS v3.1 Published 2026-03-25
Fix available
A fix is available. Upgrade to 3.7.8 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
A SQL Injection vulnerability has been found in Support Board v3.7.7. This vulnerability allows an attacker to retrieve, create, update and delete database via 'calls[0][message_ids][]' parameter in '/supportboard/include/ajax.php' endpoint.

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

SQL Injection vulnerability in Support Board v3.7.7 allows unauthenticated attackers to manipulate database queries through the 'calls[0][message_ids][]' parameter in the /supportboard/include/ajax.php endpoint, enabling data exfiltration, modification, or deletion.

MitigationUpgrade to a patched version of Support Board that implements proper input sanitization and uses parameterized queries/prepared statements for database operations. If no patch is available, implement WAF rules to block SQL injection patterns in this endpoint.

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.7.8

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify Support Board version
    Locate the version file or header in the Support Board installation (typically in the main supportboard directory, often named version.php or shown in the admin dashboard)
    Affected if The installed version is below 3.7.8 (e.g., 3.7.7 or earlier)
  2. Verify ajax.php exists
    Check for the existence of /supportboard/include/ajax.php in the web root
    Affected if The file exists and is accessible via HTTP/HTTPS
  3. Confirm parameter handling
    Examine the ajax.php code to see how the 'calls[0][message_ids][]' parameter is processed and whether it is used in SQL queries without prepared statements or parameterization
    Affected if The parameter is directly concatenated into SQL queries without sanitization or parameterized binding
  4. Test parameter injection
    Send a crafted request to ajax.php with the 'calls[0][message_ids][]' parameter containing SQL metacharacters (e.g., single quote) and observe if SQL errors are returned or timing delays occur
    Affected if The application returns SQL syntax errors or exhibits time-based SQL injection behavior
  5. Check database user privileges
    Review the database configuration used by Support Board to determine if the application database user has excessive privileges (e.g., SELECT, INSERT, UPDATE, DELETE on multiple schemas)
    Affected if The database user has broad permissions that could allow an attacker to retrieve, modify, or delete data beyond the application's scope

The environment is affected if Support Board version is below 3.7.8 AND the ajax.php endpoint handles the calls[0][message_ids][] parameter without proper input sanitization or SQL parameterization.

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.7.8 or later
Fixed in 3.7.8
Interim mitigation

Upgrade to a patched version of Support Board that implements proper input sanitization and uses parameterized queries/prepared statements for database operations. If no patch is available, implement WAF rules to block SQL injection patterns in this endpoint.

Recommended fix High confidence

Support Board 3.7.8 or later

  1. 1. Backup your current Support Board installation and database before making any changes.
  2. 2. Download Support Board version 3.7.8 or later from the official vendor website.
  3. 3. Replace the existing /supportboard directory with the new version files, or use the vendor's update mechanism if available.
  4. 4. Verify the application functions correctly after the upgrade.
  5. 5. Test that the /supportboard/include/ajax.php endpoint no longer accepts SQL injection via the 'calls[0][message_ids][]' parameter.

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

Fix this in Support Board 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-4815 — 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-4815 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