dbcve.org
SugarcrmApplication

CVE-2023-46816

HIGH · 8.8 CVSS v3.1 Published 2023-10-27
Fix available
A fix is available. Upgrade to 12.0.4 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
An issue was discovered in SugarCRM 12 before 12.0.4 and 13 before 13.0.2. A Server Site Template Injection (SSTI) vulnerability has been identified in the GecControl action. By using a crafted request, custom PHP code can be injected via the GetControl action 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 confidence

A Server-Side Template Injection (SSTI) vulnerability in SugarCRM's GetControl action allows authenticated regular users to inject arbitrary PHP code via crafted requests due to missing input validation on user-supplied parameters.

MitigationApply vendor patches (SugarCRM 12.0.4 or 13.0.2) or implement strict input validation/sanitization on the GetControl action parameters to prevent code injection.

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
SugarcrmApplication
Affected:>= 12.0.0, < 12.0.4= 13.0.0= 13.0.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed SugarCRM version
    Check the version file typically located at include/utils.php or in the SugarCRM admin panel under 'About' or 'System Information'. Alternatively, query the database version table if accessible.
    Affected if The installed version is 12.0.0, 12.0.1, 12.0.2, 12.0.3, 13.0.0, or 13.0.1.
  2. Verify GetControl action is present
    Inspect the SugarCRM application source code for the GetControl action file, typically found under modules/<module>/GetControl.php or in the controller handling GetControl requests.
    Affected if The GetControl action file exists in the installation and processes user-supplied parameters.
  3. Confirm user authentication is required
    Review the authentication requirements for the GetControl endpoint. The vulnerability states it affects authenticated regular users, so verify that the endpoint enforces authentication.
    Affected if The GetControl action accepts requests from authenticated users (regular users, not necessarily administrators).

If the installed SugarCRM version is 12.0.0 through 12.0.3, 13.0.0, or 13.0.1 and the GetControl action is accessible to authenticated users, the environment is affected by this SSTI vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 12.0.4 or later
Fixed in 12.0.4
Interim mitigation

Apply vendor patches (SugarCRM 12.0.4 or 13.0.2) or implement strict input validation/sanitization on the GetControl action parameters to prevent code injection.

Recommended fix High confidence

SugarCRM 12.0.4 or 13.0.2 (depending on your major version branch)

  1. 1. Review the SugarCRM release notes for version 12.0.4 (or 13.0.2 if on the v13 line) to understand any migration requirements
  2. 2. Perform a complete backup of the SugarCRM database, codebase, and configuration files
  3. 3. Test the upgrade in a non-production environment first
  4. 4. Deploy the upgrade to production: For v12, upgrade to 12.0.4; For v13, upgrade to 13.0.2
  5. 5. Verify the upgrade was successful and the GetControl action no longer accepts arbitrary code injection
  6. 6. Confirm normal SugarCRM functionality is intact
Caveat Review release notes for v12.0.4 or v13.0.2 for any configuration or migration changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sugarcrm Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-46816 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-46816 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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