dbcve.org
InjectionWeakness · CWE-74

CVE-2026-6982

MEDIUM · 6.3 CVSS v3.1 Published 2026-04-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
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 vulnerability was determined in star7th ShowDoc up to 2.10.10/3.6.2/3.8.0. Affected by this vulnerability is an unknown functionality of the file server/Application/Api/Controller/PageController.class.PHP of the component API Page Sort Endpoint. Executing a manipulation of the argument pages can lead to sql injection. The attack may be launched remotely. Upgrading to version 3.8.1 addresses this issue. It is suggested to upgrade the affected component. According to the researcher, "[t]he vendor explicitly stated they will not backport patches to the older affected versions."

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

SQL injection vulnerability in ShowDoc's API Page Sort Endpoint (PageController.class.php) allows remote attackers to inject malicious SQL queries via the 'pages' parameter. The vulnerability exists in the file server component and affects versions up to 2.10.10, 3.6.2, and 3.8.0.

MitigationUpgrade ShowDoc to version 3.8.1 or later to remediate. Note that the vendor will not backport patches to older affected versions, requiring a full version upgrade rather than a targeted patch.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

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

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 ShowDoc installation exists
    Look for ShowDoc installation directories (commonly under /var/www/showdoc, /www/wwwroot/showdoc, or similar web root paths). Check for the presence of server/web/index.php or the file_server directory.
    Affected if ShowDoc is installed on the system
  2. Determine installed ShowDoc version
    Check the version file typically located at public/version.json or web/version.html in the ShowDoc installation directory. Alternatively, check the version number displayed on the login page or in the admin panel.
    Affected if The installed version is 2.10.10 or lower, 3.6.2 or lower, or 3.8.0 or lower
  3. Confirm file server component is enabled
    Examine the configuration file (commonly server/Application/Common/Conf/config.php or similar) and look for the file_server_enabled setting or check if the file_server/ directory is accessible via the web server.
    Affected if The file server component is enabled and accessible via network
  4. Test for vulnerable endpoint accessibility
    Attempt to access the API endpoint via HTTP request to the file server component. The vulnerable path is typically /server/index.php?s=/api/page/sort in versions 2.x, or /web/index.php?s=/api/page/sort in versions 3.x. Check if the pages parameter accepts input.
    Affected if The API Page Sort endpoint is reachable and accepts the pages parameter

A user is affected if ShowDoc is installed with file server enabled and the version is 2.10.10 or lower, 3.6.2 or lower, or 3.8.0 or lower.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade ShowDoc to version 3.8.1 or later to remediate. Note that the vendor will not backport patches to older affected versions, requiring a full version upgrade rather than a targeted patch.

Recommended fix Moderate confidence

3.8.1

  1. Back up your existing ShowDoc database and configuration files
  2. Download ShowDoc version 3.8.1 from the official repository (github.com/star7th/showdoc)
  3. Replace the existing installation files with the new version 3.8.1 files
  4. Run any available database migration scripts included in the 3.8.1 release
  5. Verify the installation by accessing the application and testing the API Page Sort functionality
  6. Confirm the upgrade was successful by checking that the /server/Application/Api/Controller/PageController.class.php file is the 3.8.1 version
Caveat Minor version upgrades may introduce UI or API changes; review release notes before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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