dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-5261

HIGH · 7.3 CVSS v3.1 Published 2026-04-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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
A vulnerability was identified in Shandong Hoteam InforCenter PLM up to 8.3.8. The impacted element is the function uploadFileToIIS of the file /Base/BaseHandler.ashx. The manipulation of the argument File leads to unrestricted upload. It is possible to initiate the attack remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

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

Unrestricted file upload vulnerability in Shandong Hoteam InforCenter PLM (versions up to 8.3.8) within the uploadFileToIIS function of /Base/BaseHandler.ashx. The function fails to properly validate uploaded file types, names, or content, allowing remote attackers to upload malicious files (such as web shells) to the server's web root.

MitigationImplement strict server-side file validation including allowlist-based file type checking, file content/magic byte verification, random filename generation, and restrict upload directories to prevent execution. Consider disabling script execution in upload directories.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify Shandong Hoteam InforCenter PLM installation
    Locate the application installation directory - common paths may include C:\InforCenter\ or custom install paths. Check for the presence of InforCenter PLM application files and the BaseHandler.ashx file.
    Affected if The product is installed and the web application is accessible on the server.
  2. Check installed PLM version
    Examine version information in the installation directory, typically found in a version.txt, about dialog, or assembly metadata within the web application's bin folder. Compare the version number to 8.3.8.
    Affected if The installed version is 8.3.8 or lower.
  3. Verify vulnerable handler exists
    Locate the file BaseHandler.ashx in the web application's Base directory. Check if the file exists at the web root path such as /Base/BaseHandler.ashx or within the application's URL structure.
    Affected if The BaseHandler.ashx file exists and is accessible via the web server.
  4. Check if upload functionality is enabled
    Review the BaseHandler.ashx configuration and code if accessible. Look for the uploadFileToIIS function and verify whether the upload endpoint is exposed and functional in the deployed application.
    Affected if The upload function in BaseHandler.ashx is accessible and processing requests.

If Shandong Hoteam InforCenter PLM version 8.3.8 or lower is installed with the BaseHandler.ashx upload functionality exposed, the environment is affected by this vulnerability.

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

Implement strict server-side file validation including allowlist-based file type checking, file content/magic byte verification, random filename generation, and restrict upload directories to prevent execution. Consider disabling script execution in upload directories.

Recommended fix Moderate confidence
  1. Disable the /Base/BaseHandler.ashx endpoint at the IIS/web server level if not required for business operations
  2. If the endpoint is required, implement IP allowlisting at the web application firewall or network level to restrict access to trusted IPs only
  3. Restrict file upload permissions for the IIS application pool identity to prevent execution of uploaded files
  4. Move the Shandong Hoteam InforCenter PLM system behind a VPN or private network with strict access controls
  5. Monitor web server logs for unusual upload activity to the BaseHandler.ashx endpoint
  6. Audit user accounts and remove unnecessary privileges to minimize attack surface
  7. Contact the vendor through alternative channels (phone, support portal with tracking number) and document the attempt to obtain a patch

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

Have this fixed 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 help mitigating

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-2026-5261 — 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-5261 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