CVE-2023-45740
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 · uneditedStored cross-site scripting vulnerability when processing profile images exists in GROWI versions prior to v4.1.3. If this vulnerability is exploited, an arbitrary script may be executed on the web browser of the user who accessed the site using the product.
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 confidenceA stored cross-site scripting (XSS) vulnerability exists in GROWI versions prior to v4.1.3, specifically in the profile image processing functionality. Attackers can embed malicious JavaScript into uploaded profile images, which will execute in the browsers of other users who view the profile.
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< 4.1.3CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 administration panel or check the package.json/version file in the GROWI installation directory. If using Docker, check the container image tag.Affected if The installed version is lower than v4.1.3 (for example, v4.1.2, v4.1.1, v4.0.x, etc.)
-
Verify profile image upload is enabledNavigate to GROWI administration settings and check the configuration for user profile settings. Look for options related to profile image upload, avatar upload, or user profile picture functionality.Affected if Profile image upload functionality is enabled and accessible to users
-
Confirm user profile access is permittedCheck if the /user/{username} profile page is accessible. Attempt to access a user profile page or verify in admin settings that users can view each other's profiles.Affected if User profile pages are publicly or internally viewable by other users
-
Check for custom image processing configurationsInspect the GROWI configuration files (config.yml, environment variables, or admin settings) for any custom image processing middleware or security settings that may affect profile image handling.Affected if Standard GROWI profile image processing is in use without custom sanitization filters
You are affected if your GROWI installation is version v4.1.3 or earlier and the profile image upload feature is enabled for 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.
dbcve · scoped4.1.3
Upgrade GROWI to version v4.1.3 or later to remediate this vulnerability.
GROWI v4.1.3
- Backup your current GROWI installation and database before upgrading
- Upgrade GROWI to version 4.1.3 or later
- Verify the upgrade was successful by checking the GROWI version in the admin panel
- Test the profile image upload functionality to confirm the XSS vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-45740 — 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-2023-45740 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