# CVE-2017-12775: Business logic in n/a

> Remote attackers can create multiple user accounts in Question2Answer due to insufficient validation in the installation script.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-x5v6-qg9c-phr7

## What is CVE-2017-12775?

CVE-2017-12775 is a high-severity vulnerability in n/a, published on 29 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

qa-include/qa-install.php in Question2Answer before 1.7.5 allows remote attackers to create multiple user accounts.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Question2answer Question2answer.

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

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

## Is CVE-2017-12775 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-12775 is a high-severity vulnerability in n/a, published on 29 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-12775 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-2017-12775/ (Markdown: https://insights.sbomify.com/CVE-2017-12775/index.md)
```

## Sources

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

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