CVE-2018-15847
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 · uneditedAn issue was discovered in puppyCMS 5.1. There is an XSS vulnerability via menu.php in the "Add Page/URL" URL link field.
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 confidenceA stored Cross-Site Scripting (XSS) vulnerability exists in puppyCMS 5.1 within menu.php. The 'Add Page/URL' URL link field does not properly sanitize user input, allowing malicious JavaScript to be injected and stored. When other users view the affected menu, the injected script executes in their browser session.
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= 5.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
- 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.
-
Identify the installed puppyCMS versionCheck the version file or admin dashboard for the running puppyCMS version numberAffected if The installed version is exactly 5.1
-
Verify menu.php exists and is accessibleLocate the menu.php file in the web root or admin directory and confirm it is present on the systemAffected if menu.php exists in the puppyCMS installation
-
Inspect the URL link field handling in menu.phpExamine the source code of menu.php to determine if the URL link field accepts user input without proper sanitization or validationAffected if The URL link field in the Add Page/URL function lacks input sanitization or output encoding
-
Check database for menu entries with script contentQuery the database for menu-related tables and inspect the URL/link field for any stored JavaScript tags, script elements, or HTML tags that may indicate exploitationAffected if The database contains menu entries with unsanitized JavaScript or HTML in URL fields that could execute in a browser
-
Determine if menus are viewable by other usersVerify whether the menu functionality displays stored URLs to authenticated users or public visitors without re-encoding the outputAffected if Menus are displayed to users without proper output encoding, allowing stored scripts to execute
A user is affected if they are running puppyCMS version 5.1, the menu.php file is present, and either the URL link field lacks sanitization or malicious script content already exists in the menu database records that would render to other users.
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 on the URL link field in menu.php. All user-supplied input should be sanitized using allowlist validation and HTML entity encoding before storage and display.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-15847 — 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-15847 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