CVE-2023-46815
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 SugarCRM 12 before 12.0.4 and 13 before 13.0.2. An Unrestricted File Upload vulnerability has been identified in the Notes module. By using a crafted request, custom PHP code can be injected via the Notes module because of missing input validation. An attacker with regular user privileges can exploit this.
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 confidenceAn Unrestricted File Upload vulnerability in SugarCRM's Notes module (versions 12.x < 12.0.4 and 13.x < 13.0.2) allows authenticated regular users to inject custom PHP code due to missing input validation on file uploads. The attacker can upload malicious PHP files through the Notes functionality, potentially achieving remote code execution.
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>= 12.0.0, < 12.0.4= 13.0.0= 13.0.1CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 SugarCRM versionAccess the SugarCRM About page (typically /index.php?module=About) or check the version.php config file in the application root directoryAffected if The installed version is 12.0.0 through 12.0.3, or 13.0.0 through 13.0.1 (versions below 12.0.4 or 13.0.2)
-
Verify Notes module is enabledLog in as an administrator and navigate to Admin > Module Loader or check the module visibility settings for the Notes moduleAffected if The Notes module is enabled and visible to regular (non-admin) users in the application
-
Confirm regular user access to Notes upload featureLog in as a regular (non-admin) user and attempt to access the Notes module. Check if the user can create a new Note with a file attachmentAffected if Regular authenticated users can access the Notes module and the file upload/create functionality
-
Inspect upload directory PHP execution settingsLocate the directory where uploaded files are stored (check config.php or upload.php for the upload_dir path). Verify that .htaccess or server configuration prevents PHP execution in that directoryAffected if PHP files can be executed from the upload directory (no restrictions in place)
You are affected if your SugarCRM version is below 12.0.4 or 13.0.2 AND the Notes module is enabled with file upload access available to regular 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 · scoped12.0.4
Upgrade SugarCRM to version 12.0.4 or 13.0.2 or later. Additionally, implement strict file type validation and disable PHP execution in upload directories as defense-in-depth measures.
12.0.4 or later for 12.x branches; 13.0.2 or later for 13.x branches
- Create a complete backup of the SugarCRM database and files
- Upgrade SugarCRM 12.x to version 12.0.4 or later
- If running 13.0.0 or 13.0.1, upgrade to version 13.0.2 or later
- After upgrade, verify the Notes module functionality works correctly
- Confirm the upgrade was successful by checking the SugarCRM version in About section
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46815 — 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-46815 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