CVE-2023-31223
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 · uneditedDradis before 4.8.0 allows persistent XSS by authenticated author users, related to avatars.
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 confidenceDradis before 4.8.0 contains a stored (persistent) cross-site scripting vulnerability in the avatar upload functionality. Authenticated author users can upload malicious avatar images containing embedded JavaScript payloads that execute when other users view the profile, allowing session hijacking or further attacks against other authenticated users.
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.8.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
- 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 Dradis versionLocate the installed Dradis version by checking the application documentation, version file, or using the Dradis CLI version command if availableAffected if The installed version is earlier than 4.8.0 (e.g., 4.7.0, 4.6.0, etc.)
-
Verify avatar upload is accessibleLog into the Dradis instance and navigate to the user profile or account settings area where avatar upload functionality is presentAffected if Avatar upload functionality is enabled and accessible to authenticated users
-
Confirm author-level accounts existCheck the Dradis user management panel or user directory to identify if there are accounts with author-level privilegesAffected if Author-level user accounts exist in the Dradis instance
-
Inspect avatar upload handlingIf you have access, examine the avatar upload endpoint or code to see if it performs proper file type validation and sanitization on uploaded imagesAffected if Uploaded avatars are not validated for malicious content (e.g., embedded scripts) before storage and display
You are affected if your Dradis installation version is below 4.8.0 and the avatar upload feature is accessible to authenticated author 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.8.0
Upgrade to Dradis version 4.8.0 or later, which implements proper input validation and sanitization for avatar uploads. Until upgraded, limit or monitor avatar upload functionality for author-level accounts.
Dradis 4.8.0 or later
- 1. Back up the current Dradis installation and database before upgrading
- 2. Obtain Dradis version 4.8.0 or later from the official Dradis framework repository
- 3. Follow the standard Dradis upgrade procedure for your installation method (gem, Docker, or source)
- 4. Verify the upgrade was successful by checking the Dradis version in the web interface or via CLI
- 5. Test the avatar upload functionality to confirm the XSS vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2023-31223 — 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-31223 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