CVE-2018-10219
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 · uneditedbaijiacms V3 has physical path leakage via an index.php?mod=mobile&name=member&do=index request.
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 confidencebaijiacms V3 leaks the server's physical file path when processing a specific mobile member index request (index.php?mod=mobile&name=member&do=index). This information disclosure occurs through verbose error output or debug messages that expose absolute filesystem paths, potentially aiding attackers in reconnaissance for further exploitation.
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= 3.0CVSS 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.0/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 Baijiacms installationLook for the presence of index.php in the web root and check for 'baijiacms' or 'Baijiacms' strings in the application. Check the version file or footer of admin pages for version 3.0.Affected if Baijiacms V3 (version 3.0) is installed and running.
-
Verify mobile module is accessibleCheck if the /mobile/ directory or mobile routing is enabled by attempting to access any index.php?mod=mobile URL on the server.Affected if The mobile module functionality is enabled and reachable via web requests.
-
Trigger the vulnerable endpointSend an HTTP request to index.php?mod=mobile&name=member&do=index and capture the response. This can be done via curl, browser, or any HTTP client.Affected if The request completes and returns a response containing the page output.
-
Inspect response for path disclosureExamine the HTTP response body and any error messages, warnings, or debug output for absolute filesystem paths (paths starting with / on Linux or drive letters like C:\ on Windows).Affected if The response contains absolute server filesystem paths in error messages, warnings, stack traces, or debug output.
A server is affected if Baijiacms V3.0 is running with the mobile module accessible and the specific endpoint index.php?mod=mobile&name=member&do=index returns responses that expose absolute filesystem paths.
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 dataConfigure custom error handlers to suppress detailed error messages in production, and ensure the application uses relative paths or generic error responses rather than exposing server filesystem paths.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-10219 — 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-2018-10219 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