CVE-2023-29376
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 · uneditedAn issue was discovered in Progress Sitefinity 13.3 before 13.3.7647, 14.0 before 14.0.7736, 14.1 before 14.1.7826, 14.2 before 14.2.7930, and 14.3 before 14.3.8025. There is potential XSS by privileged users in Sitefinity to media libraries.
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 confidenceThis is a stored Cross-Site Scripting (XSS) vulnerability in Progress Sitefinity CMS affecting media library functionality. Privileged (authenticated) users can inject malicious JavaScript code through media library fields that gets stored and executed when other users view the content. The vulnerability affects multiple version branches (13.3, 14.0, 14.1, 14.2, 14.3) before their respective patched releases.
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>= 13.3, < 13.3.7646>= 14.0, < 14.0.7736>= 14.1, < 14.1.7826>= 14.2, < 14.2.7930>= 14.3, < 14.3.8026CVSS 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 Sitefinity versionLocate the Sitefinity assembly version. Check the bin folder for Telerik.Sitefinity.dll or examine the version through the Sitefinity administration dashboard under Administration > Version. Compare against affected ranges: 13.3.x < 13.3.7646, 14.0.x < 14.0.7736, 14.1.x < 14.1.7826, 14.2.x < 14.2.7930, 14.3.x < 14.3.8026.Affected if Installed version falls within any of the affected version ranges.
-
Confirm media library feature is activeLog into the Sitefinity backend and navigate to Content > Media to verify the media library module is enabled and contains any libraries or uploaded content.Affected if Media library functionality is present and contains uploaded content.
-
Inspect media library entries for suspicious contentAccess the media library through the administration panel and review uploaded file metadata (title, description, alternative text, tags). Look for unexpected HTML tags, script elements, or javascript: URIs in these fields.Affected if Any media library entries contain script tags, event handlers, or suspicious JavaScript code in metadata fields.
-
Review user roles with media upload permissionsNavigate to Administration > Users > Roles in the Sitefinity backend. Identify which roles have permissions to create or edit media library content.Affected if Multiple privileged users exist with media library upload capabilities, increasing exposure to injected XSS payloads.
-
Check for recent media library modificationsReview Sitefinity audit logs or activity logs for recent media library uploads, particularly those made by privileged users. Inspect the timestamp and user account of recent uploads.Affected if Media items were recently uploaded by privileged users and the system is running an affected version.
The environment is affected if the installed Sitefinity version matches any of the vulnerable ranges AND the media library feature is in use with privileged user access possible.
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 · scoped13.3.764614.0.773614.1.7826
Update Sitefinity to version 13.3.7647 or later, 14.0.7736 or later, 14.1.7826 or later, 14.2.7930 or later, or 14.3.8025 or later. As a compensating control, implement strict input validation and output encoding on media library upload/display paths.
Minimum fixed versions: 13.3.7647, 14.0.7736, 14.1.7826, 14.2.7930, or 14.3.8025 (choose based on current branch)
- 1. Identify the current Sitefinity version by navigating to Administration > Settings > Version in the Sitefinity CMS admin interface
- 2. Based on your current version branch, determine the target fixed version: for 13.3.x upgrade to 13.3.7647 or later; for 14.0.x upgrade to 14.0.7736 or later; for 14.1.x upgrade to 14.1.7826 or later; for 14.2.x upgrade to 14.2.7930 or later
- 3. Perform a complete backup of the Sitefinity database and website files before upgrading
- 4. Download the corresponding Sitefinity NuGet package or use the Sitefinity CMS upgrade wizard
- 5. Apply the upgrade following Progress documentation for your specific version path
- 6. After upgrade, verify the XSS vulnerability is resolved by testing media library functionality with potential XSS payloads
- 7. Clear all caches and restart the application pools
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-29376 — 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-29376 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