# CVE-2017-14508: SQL injection in n/a

> Authenticated users can exploit SQL injection in SugarCRM Documents and Emails modules to modify the database.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7mw8-x3cx-f3rv

## What is CVE-2017-14508?

CVE-2017-14508 is a high-severity SQL injection vulnerability in Sugarcrm Sugarcrm, published on 17 Sep 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in SugarCRM before 7.7.2.3, 7.8.x before 7.8.2.2, and 7.9.x before 7.9.2.0 (and Sugar Community Edition 6.5.26). Several areas have been identified in the Documents and Emails module that could allow an authenticated user to perform SQL injection, as demonstrated by a backslash character at the end of a bean_id to modules/Emails/DetailView.php. An attacker could exploit these vulnerabilities by sending a crafted SQL request to the affected areas. An exploit could allow the attacker to modify the SQL database. Proper SQL escaping has been added to prevent such exploits.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2017-14508?

It affects 1 product.


Products: Sugarcrm Sugarcrm.

## How do I fix CVE-2017-14508?

No fix has been published for CVE-2017-14508 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-14508 being exploited?

There is no known exploitation of CVE-2017-14508 in the wild and no public exploit code.

## Other vulnerabilities in Sugarcrm Sugarcrm

- [CVE-2023-22952](https://insights.sbomify.com/CVE-2023-22952/): Multiple SugarCRM Products Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2004-1225](https://insights.sbomify.com/CVE-2004-1225/): SQL injection in n/a (critical 10.0)
- [CVE-2020-7472](https://insights.sbomify.com/CVE-2020-7472/): Path traversal in n/a (critical 9.8)
- [CVE-2012-0694](https://insights.sbomify.com/CVE-2012-0694/): Deserialization in n/a (critical 9.8)
- [CVE-2014-3244](https://insights.sbomify.com/CVE-2014-3244/): XML external entity in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-14508 and fix it if it is affected.

What it is: CVE-2017-14508 is a high-severity SQL injection vulnerability in Sugarcrm Sugarcrm, published on 17 Sep 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-14508 in the wild and no public exploit code.

Affected product: Sugarcrm Sugarcrm. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-14508/ (Markdown: https://insights.sbomify.com/CVE-2017-14508/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-14508
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-14508
- OSV: https://osv.dev/vulnerability/CVE-2017-14508

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-14508/
Summaries are generated and may contain mistakes; the official description above is the record.