dbcve.org
MaxboardApplication · Maxb

CVE-2021-26633

CRITICAL · 9.8 CVSS v3.1 Published 2022-06-02
Fix available
A fix is available. Upgrade to 1.9.4 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
SQL injection and Local File Inclusion (LFI) vulnerabilities in MaxBoard can cause information leakage and privilege escalation. This vulnerabilities can be exploited by manipulating a variable with a desired value and inserting and arbitrary file.

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

MaxBoard versions prior to a fix contain both SQL injection and Local File Inclusion (LFI) vulnerabilities. The SQL injection allows attackers to manipulate database queries for information disclosure or privilege escalation, while the LFI permits reading or including arbitrary files on the server by manipulating variable values.

MitigationApply available vendor patches for MaxBoard; if no patch exists, implement strict input validation and whitelist-based filtering on all user-controlled variables to block SQL injection and LFI exploitation paths.

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
MaxboardApplication
Affected:< 1.9.4

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. Identify MaxBoard installation version
    Locate the MaxBoard installation directory and find the version file or banner. Common locations include a version.php, about page in the admin panel, or a config/version file. Alternatively, check the HTTP response headers or the application footer for version information.
    Affected if The installed version is less than 1.9.4
  2. Verify SQL injection attack surface
    Review the application's database query handlers, particularly any endpoints that accept user-controlled parameters and pass them to SQL queries without prepared statements or parameter binding. Check login, search, filtering, or comment functions.
    Affected if User input is directly concatenated into SQL queries without sanitization or parameterized queries, and the MaxBoard version is below 1.9.4
  3. Verify LFI attack surface
    Examine file inclusion or file loading functionality in the application. Look for endpoints that accept file paths or file names as parameters and include or require them. Check for variables that can be manipulated to traverse directories or access system files.
    Affected if File inclusion functions accept unsanitized user input for file paths, and the MaxBoard version is below 1.9.4
  4. Confirm web server configuration
    Check if MaxBoard is directly accessible and the web server is configured to process PHP files. Review the web root where MaxBoard is installed and confirm the application is actively handling HTTP requests.
    Affected if MaxBoard is running as a web application and the vulnerabilities can be exploited via HTTP requests

If MaxBoard version is confirmed to be below 1.9.4 and the application processes user-supplied input through database queries or file inclusion functions without strict validation, the environment is vulnerable to both SQL injection and LFI attacks described in this CVE.

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

Apply available vendor patches for MaxBoard; if no patch exists, implement strict input validation and whitelist-based filtering on all user-controlled variables to block SQL injection and LFI exploitation paths.

Recommended fix Moderate confidence

MaxBoard 1.9.4

  1. 1. Backup your current MaxBoard installation and database before making any changes
  2. 2. Identify your current MaxBoard version by checking the admin panel or version file
  3. 3. Download MaxBoard version 1.9.4 from the official vendor source
  4. 4. Replace the existing MaxBoard files with the new version 1.9.4 files
  5. 5. Verify the upgrade was successful by checking the version in the admin panel
  6. 6. Test that SQL injection and LFI vulnerabilities are no longer exploitable
  7. 7. Monitor logs for any unusual activity that may indicate prior compromise

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

Fix this in Maxboard Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,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 $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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