CVE-2018-10296
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 · uneditedMiniCMS V1.10 has XSS via the mc-admin/post-edit.php title parameter.
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 confidenceMiniCMS V1.10 contains a stored Cross-Site Scripting (XSS) vulnerability in the admin panel. The title parameter in mc-admin/post-edit.php does not properly sanitize user-supplied input before rendering it, allowing authenticated administrators to inject malicious JavaScript code that executes when the post is viewed.
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= 1.10CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Confirm MiniCMS installation and versionLocate MiniCMS installation directory and check for version indicators such as version.php, readme.txt, or a VERSION file. Alternatively, examine the source code for a version constant or variable.Affected if MiniCMS version 1.10 is installed
-
Verify vulnerable file existsCheck for the presence of mc-admin/post-edit.php in the web root or MiniCMS installation directory.Affected if The file mc-admin/post-edit.php exists in the expected location
-
Confirm admin panel accessibilityAttempt to access the admin panel directory mc-admin/ via HTTP request to verify it is accessible on the server.Affected if The admin panel at mc-admin/ is accessible and does not return a 403 or 404 error
-
Identify saved posts with title fieldExamine the database or content storage mechanism used by MiniCMS to list existing posts. Look for records in the posts table that contain a title field.Affected if There are existing posts stored in the system, as the XSS is stored and triggers when a post is viewed
A user is affected if they have MiniCMS version 1.10 installed with the mc-admin/post-edit.php file present and the admin panel accessible, particularly if any posts have been created or edited through the vulnerable title parameter.
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 input validation and output encoding for the title parameter in post-edit.php. Use context-appropriate escaping when rendering the title field in all affected views.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-10296 — 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-10296 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