# CVE-2017-17693: Missing authorization in n/a

> Attackers can delete feedback entries without authorization due to missing access controls in the portfolio management panel.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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:** 15 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jc5f-jq4r-gpw4

## What is CVE-2017-17693?

CVE-2017-17693 is a medium-severity missing authorization vulnerability in n/a, published on 15 Dec 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Techno - Portfolio Management Panel through 2017-11-16 does not check authorization for panel/portfolio.php?action=delete requests that remove feedback.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Techno - Portfolio Management Panel Project Techno - Portfolio Management Panel.

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

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

## Is CVE-2017-17693 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-17110](https://insights.sbomify.com/CVE-2017-17110/): SQL injection in n/a (critical 9.8)
- [CVE-2017-17695](https://insights.sbomify.com/CVE-2017-17695/): SQL injection in n/a (high 8.8)
- [CVE-2017-17694](https://insights.sbomify.com/CVE-2017-17694/): Cross-site scripting in n/a (medium 5.4)
- [CVE-2017-17696](https://insights.sbomify.com/CVE-2017-17696/): Information disclosure in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-17693 is a medium-severity missing authorization vulnerability in n/a, published on 15 Dec 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-17693 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-17693/ (Markdown: https://insights.sbomify.com/CVE-2017-17693/index.md)
```

## Sources

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

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