CVE-2023-6100
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 vulnerability classified as problematic was found in Maiwei Safety Production Control Platform 4.1. This vulnerability affects unknown code of the file /api/DataDictionary/GetItemList. The manipulation leads to information disclosure. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. VDB-245062 is the identifier assigned to this vulnerability. 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 confidenceAn information disclosure vulnerability exists in the Maiwei Safety Production Control Platform 4.1 at the /api/DataDictionary/GetItemList endpoint. The vulnerability allows remote unauthenticated attackers to access potentially sensitive data through this API endpoint.
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= 4.1CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Maiwei Safety Production Control Platform is installedCheck system inventory, installed applications, or consult the vendor documentation for the platform to confirm presence of Maiwei Safety Production Control Platform version 4.1Affected if The platform version is 4.1 and it is installed in the environment
-
Verify the exact installed versionConsult the platform's about page, version information file, or administrative interface to confirm the running version number is exactly 4.1Affected if The installed version is confirmed to be 4.1
-
Confirm the vulnerable API endpoint existsAttempt to access the URL path /api/DataDictionary/GetItemList on the server hosting the platform (e.g., http://target/api/DataDictionary/GetItemList or https://target/api/DataDictionary/GetItemList)Affected if The endpoint responds with HTTP 200 or any data without requiring login credentials
-
Check if the endpoint returns data without authenticationSend a request to /api/DataDictionary/GetItemList without providing any authentication tokens, session cookies, or credentials and observe whether the response contains data (such as data dictionary items, system configuration data, or other potentially sensitive information)Affected if The endpoint returns any data or system information without requiring authentication
The environment is affected if Maiwei Safety Production Control Platform version 4.1 is installed and the /api/DataDictionary/GetItemList endpoint is accessible without authentication and returns data.
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.
From vendor dataImplement proper authentication and authorization controls on the affected API endpoint. If vendor patch is unavailable, restrict network access to the API or deploy a WAF rule to block unauthorized access to /api/DataDictionary/GetItemList.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2023-6100 — 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-2023-6100 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