CVE-2017-9361
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 · uneditedWebsiteBaker v2.10.0 has a stored XSS vulnerability in /account/details.php.
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 in WebsiteBaker CMS v2.10.0 within the /account/details.php file allows attackers to inject malicious JavaScript code through user input fields. This payload persists on the server and executes when other users (including administrators) view the account details page.
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= 2.10.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
- 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 WebsiteBaker CMS installationIdentify if WebsiteBaker CMS is present on the server by checking for typical installation directories or by accessing the website and looking for WebsiteBaker branding in the page source or login page.Affected if WebsiteBaker CMS is installed and accessible on the server.
-
Check installed WebsiteBaker versionLocate the version file or dashboard within WebsiteBaker admin panel, typically found in the admin settings or footer of the control panel. Alternatively, check version.php in the include or config directory if file access is available.Affected if The installed version is exactly 2.10.0.
-
Verify account details module existsCheck for the presence of /account/details.php file in the web root or document directory. This file handles user profile or account detail display.Affected if The file /account/details.php exists and is accessible via web request.
-
Confirm user account functionality is enabledAttempt to access the account details page through the web interface (typically at /account/details.php or /pages/accountdetails.php) or check the pages table in the database for account-related pages.Affected if User account details page is accessible and functional for registered users.
-
Inspect user input fields in account detailsLog in as a regular user and navigate to the account details page. Examine the HTML source of the form fields (first name, last name, display name, etc.) to identify unencoded user-supplied data.Affected if User-supplied data from profile fields is reflected in the page without proper HTML encoding.
A user is affected if WebsiteBaker CMS version 2.10.0 is installed and the account details functionality (/account/details.php) is accessible, allowing stored XSS payloads to persist and execute for other users viewing account profiles.
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 contextual output encoding for all user-supplied data rendered in /account/details.php. Additionally, implement Content Security Policy (CSP) headers as a defense-in-depth measure.
- 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-2017-9361 — 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-2017-9361 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