CVE-2018-0653
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 · uneditedCross-site scripting vulnerability in GROWI v.3.1.11 and earlier allows remote attackers to inject arbitrary web script or HTML via Wiki page view.
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 confidenceStored cross-site scripting (XSS) vulnerability in GROWI v3.1.11 and earlier allows remote attackers to inject arbitrary JavaScript or HTML into wiki pages through unsanitized user input that gets rendered when users view those pages.
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.1.11CVSS 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 installed GROWI versionAccess the GROWI admin panel (usually at /admin) and navigate to the Application Settings or About page to view the version number. Alternatively, check the package.json file in the GROWI installation directory for the version field.Affected if Version displayed is 3.1.11 or earlier (any version <= 3.1.11)
-
Verify if user registration is enabledGo to GROWI admin panel under Security Settings and check if the 'Enable GitHub OAuth' or 'Enable Google OAuth' or local user registration is turned on for users outside your trusted group.Affected if User registration or OAuth is enabled, allowing untrusted users to create accounts
-
Check wiki page creation permissionsIn GROWI admin under Security Settings, examine the 'Default permission' setting for newly created pages and whether guest users (non-authenticated) can create or edit pages.Affected if Guest users have permission to create or edit wiki pages, or default page permissions allow broad editing access
-
Confirm wiki editing is activeLog in as a non-admin user or use a guest account and attempt to create a new wiki page or edit an existing one to verify the feature is accessible.Affected if The wiki page creation or editing feature is functional and accessible to users beyond administrators
You are affected if GROWI version is 3.1.11 or earlier AND the wiki page creation/editing feature is accessible to users you do not fully trust, since untrusted input can be stored and rendered as executable script.
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 dataUpgrade GROWI to version 3.1.12 or later which contains the patch. Until then, restrict wiki page creation/editing permissions to trusted users only.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0653 — 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-0653 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