dbcve.org
Maiwei Safety Production Control PlatformApplication · Maiwei Safety Production Control Platform Project

CVE-2023-6101

HIGH · 7.5 CVSS v3.1 Published 2023-11-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/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, which was classified as problematic, has been found in Maiwei Safety Production Control Platform 4.1. This issue affects some unknown processing of the file /TC/V2.7/ha.html of the component Intelligent Monitoring. The manipulation leads to information disclosure. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-245063. NOTE: 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 · moderate confidence

Information disclosure vulnerability in Maiwei Safety Production Control Platform 4.1's Intelligent Monitoring component. The /TC/V2.7/ha.html file allows remote unauthenticated attackers to access sensitive information due to improper access controls. A public exploit is available, enabling easy exploitation.

MitigationSince the vendor is unresponsive, implement network-level access controls to restrict exposure of the affected endpoint, or deploy a reverse proxy with authentication in front of the application. Conduct a thorough audit to determine what data was exposed.

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
Maiwei Safety Production Control PlatformApplication
Affected:= 4.1

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Maiwei Safety Production Control Platform is installed
    Inspect your web server, application directories, or running services for the presence of Maiwei Safety Production Control Platform. Look for associated web directories, services, or installed packages.
    Affected if The platform is present in the environment
  2. Confirm the installed version is 4.1
    Locate the version file, about page, or configuration that displays the platform version. Common locations include version info in the web interface, config files, or installation metadata.
    Affected if The installed version equals 4.1 exactly
  3. Check if the Intelligent Monitoring component is enabled
    Locate the module configuration or feature list for the platform. Verify whether the Intelligent Monitoring component is present and active in the installation.
    Affected if The Intelligent Monitoring component is enabled or present
  4. Verify the vulnerable endpoint is accessible
    Attempt to access the file /TC/V2.7/ha.html via HTTP or HTTPS request from an unauthenticated perspective. Check if the endpoint responds without requiring authentication.
    Affected if The endpoint /TC/V2.7/ha.html returns a valid response without authentication
  5. Inspect the response for sensitive information exposure
    Examine the content returned from accessing /TC/V2.7/ha.html. Look for sensitive data such as credentials, configuration details, internal network information, or personal data that should not be publicly accessible.
    Affected if The endpoint exposes sensitive information that should require authentication

A user is affected if Maiwei Safety Production Control Platform version 4.1 is installed, the Intelligent Monitoring component is enabled, and the endpoint /TC/V2.7/ha.html is accessible without authentication and exposes sensitive data.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since the vendor is unresponsive, implement network-level access controls to restrict exposure of the affected endpoint, or deploy a reverse proxy with authentication in front of the application. Conduct a thorough audit to determine what data was exposed.

Fix this in Maiwei Safety Production Control Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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