CVE-2023-29375
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 potentially dangerous file upload through the SharePoint connector.
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 confidenceProgress Sitefinity CMS contains a dangerous file upload vulnerability in the SharePoint connector component. An unauthenticated or authenticated attacker could potentially upload malicious files (e.g., web shells) through the SharePoint integration, leading to remote code execution on the affected server.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Determine installed Sitefinity versionCheck the Telerik.Sitefinity.dll assembly version in the /bin folder, or view the version in Sitefinity Administration under Administration > System > Version. Alternatively, check the AssemblyInfo.cs or project references for the Sitefinity version number.Affected if The installed version falls within any of these ranges: 13.3.x before 13.3.7646, 14.0.x before 14.0.7736, 14.1.x before 14.1.7826, 14.2.x before 14.2.7930, or 14.3.x before 14.3.8026.
-
Verify if SharePoint connector is enabledLog into Sitefinity administration and navigate to the SharePoint connector settings, typically under Administration > Settings > Advanced > SharePoint, or inspect the Sitefinity configuration XML files for the presence of the SharePoint connector module.Affected if The SharePoint connector module is installed and enabled in the Sitefinity configuration.
-
Inspect SharePoint upload directoriesLocate the configured SharePoint document library storage path on the server (check Sitefinity configuration for the UploadPath or DocumentLibraryPath setting), then list and review all files in those directories for unfamiliar or suspicious file types such as .ashx, .aspx, .php, or other executable extensions.Affected if The SharePoint connector is active and writable, and unexpected executable files are present in SharePoint-related upload directories.
-
Review recent file uploads via SharePointCheck Sitefinity activity logs or SharePoint connector logs for recent file upload events, focusing on files with extensions that could lead to code execution (.asp, .aspx, .ashx, .jsp, .php, .exe, .dll).Affected if Recent uploads include file types that should not be allowed or that indicate potential web shell placement.
You are affected if your Sitefinity version is below the fixed releases AND the SharePoint connector component is enabled and accessible to upload files.
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
Upgrade Sitefinity to version 13.3.7647 or later for 13.x, 14.0.7736 or later for 14.0.x, 14.1.7826 or later for 14.1.x, 14.2.7930 or later for 14.2.x, or 14.3.8025 or later for 14.3.x. Alternatively, disable the SharePoint connector if not in use.
13.3.7647 (or latest 13.3.x) / 14.0.7736 (or latest 14.0.x) / 14.1.7826 (or latest 14.1.x) / 14.2.7930 (or latest 14.2.x) / 14.3.8025+
- Identify your current Sitefinity version from the affected versions list (13.3.x, 14.0.x, 14.1.x, or 14.2.x)
- Plan the upgrade to the minimum fixed version for your release line: 13.3.7647, 14.0.7736, 14.1.7826, or 14.2.7930
- Backup your Sitefinity database and all site files before proceeding
- Test the upgrade in a non-production environment first
- Apply the upgrade following Progress Sitefinity's standard upgrade procedures
- Verify the SharePoint connector functionality after upgrade
- Monitor for any post-upgrade issues in production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-29375 — 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-29375 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