CVE-2023-30956
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 · uneditedA security defect was identified in Foundry Comments that enabled a user to discover the contents of an attachment submitted to another comment if they knew the internal UUID of the target attachment. This defect was resolved with the release of Foundry Comments 2.267.0.
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 confidenceFoundry Comments had an Insecure Direct Object Reference (IDOR) vulnerability where users could access attachments from other comments by knowing the internal UUID of the target attachment, enabling unauthorized disclosure of attachment contents without proper authorization checks.
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.267.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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/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 Foundry Comments versionAccess the Foundry platform administration panel or use the platform API to retrieve the installed version of the Foundry Comments application. This is typically found in the platform's application management or version information section.Affected if The installed version is lower than 2.267.0 (e.g., 2.265.0, 2.260.0, etc.)
-
Confirm Comments application is enabledVerify that the Foundry Comments application is actively enabled in your Foundry platform deployment. Check the platform services or applications list to confirm Comments is running.Affected if The Comments application is enabled and running in the environment
-
Verify attachment access functionality existsCheck if the attachment upload and access features are available in the Comments module. This can be confirmed by examining whether users can attach files to comments or access attachment URLs within the platform.Affected if Attachment functionality is available and users can access attachment URLs via direct UUID references
-
Check for unauthorized attachment access logsReview Foundry platform audit logs or access logs for any instances where attachment URLs were accessed using UUIDs that do not belong to the requesting user's comments. Look for access patterns to /attachments/* endpoints with varying UUIDs.Affected if Evidence exists of attachment access attempts using UUIDs that cross-comment boundaries without proper authorization validation
Your environment is affected if Foundry Comments version is below 2.267.0 and the attachment functionality is enabled, allowing potential unauthorized access to attachments via direct UUID references.
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 · scoped2.267.0
Upgrade Foundry Comments to version 2.267.0 or later, which includes proper authorization validation for attachment access.
2.267.0
- Upgrade Foundry Comments to version 2.267.0 or later to resolve the IDOR vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30956 — 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-30956 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