Support BoardWordPress extension · Schiocco
CVE-2026-4816
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 · uneditedA Reflected Cross Site Scripting (XSS) vulnerability has been found in Support Board v3.7.7. This vulnerability allows an attacker to execute JavaScript code in the victim's browser by sending the victim a malicious URL using the 'search' parameter in '/supportboard/include/articles.php'. This vulnerability can be exploited to steal sensitive user data, such as session cookies, or to perform actions on behalf of the user.
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 confidenceA reflected Cross Site Scripting (XSS) vulnerability in Support Board v3.7.7 allows attackers to inject malicious JavaScript through the 'search' parameter in '/supportboard/include/articles.php'. When victims click a crafted URL, the attacker's script executes in their browser, enabling session cookie theft and unauthorized actions.
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
< 3.7.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Support Board versionLocate the version information in the Support Board installation (typically found in version files, admin dashboard, or main configuration files)Affected if Version is below 3.7.8
-
Verify articles.php existsCheck if the file /supportboard/include/articles.php exists and is accessible in the web rootAffected if The file exists and is web-accessible
-
Test search parameter for reflectionSend a crafted request to /supportboard/include/articles.php with a test payload in the 'search' parameter (for example: ?search=<script>alert(1)</script>) and inspect whether the raw script tag appears in the responseAffected if The 'search' parameter value is reflected in the response without HTML encoding
-
Check code for input sanitizationReview the source code of articles.php to determine if the 'search' parameter undergoes proper input validation or output encoding before being reflectedAffected if No sanitization or encoding is applied to the 'search' parameter before reflection
A user is affected if their Support Board version is below 3.7.8 AND the articles.php file handles the 'search' parameter without proper sanitization, allowing reflected XSS.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.7.8
Apply proper input validation and output encoding to the 'search' parameter in articles.php before reflecting it in the response. Implement context-aware escaping and consider adding Content Security Policy headers.
Support Board 3.7.8 or later
- Backup the current Support Board installation and database before proceeding with the upgrade
- Download Support Board version 3.7.8 or later from the official vendor source
- Replace the existing Support Board files with the files from version 3.7.8 or later
- Verify that the /supportboard/include/articles.php file has been updated
- Test that the 'search' parameter in articles.php no longer reflects untrusted input without proper sanitization
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
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4816 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-4816 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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