# CVE-2014-8677: Code injection in n/a

> Authenticated attackers can execute arbitrary PHP code via crafted database names in SOPlanning under specific configuration conditions.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **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:** 31 Aug 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-r3rc-xgjr-hc9q

## What is CVE-2014-8677?

CVE-2014-8677 is a medium-severity code injection vulnerability in n/a, published on 31 Aug 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The installation process for SOPlanning 1.32 and earlier allows remote authenticated users with a prepared database, and access to an existing database with a crafted name, or permissions to create arbitrary databases, or if PHP before 5.2 is being used, the configuration database is down, and smarty/templates_c is not writable to execute arbitrary php code via a crafted database name.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2014-8677?

It affects 1 product.


Products: Soplanning Soplanning.

## How do I fix CVE-2014-8677?

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

## Is CVE-2014-8677 being exploited?

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

Public exploit code:

- SO Planning 1.32 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2024-27115](https://insights.sbomify.com/CVE-2024-27115/): Remote Code Execution through File Upload in SOPlanning before 1.52.02 (critical 10.0)
- [CVE-2024-57169](https://insights.sbomify.com/CVE-2024-57169/): File upload in n/a (critical 9.8)
- [CVE-2024-9574](https://insights.sbomify.com/CVE-2024-9574/): SQL Injection vulnerability in SOPlanning (critical 9.8)
- [CVE-2020-13963](https://insights.sbomify.com/CVE-2020-13963/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2014-8673](https://insights.sbomify.com/CVE-2014-8673/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-8677 and fix it if it is affected.

What it is: CVE-2014-8677 is a medium-severity code injection vulnerability in n/a, published on 31 Aug 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-2014-8677 in the wild and no public exploit code.

Affected product: n/a. 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-2014-8677/ (Markdown: https://insights.sbomify.com/CVE-2014-8677/index.md)
```

## Sources

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

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