# CVE-2018-15809: Misconfiguration in n/a

> Insecure file permissions in AccuPOS allow local attackers to modify executables, potentially leading to privilege escalation or code execution.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Aug 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-m726-p293-2jq2

## What is CVE-2018-15809?

CVE-2018-15809 is a medium-severity vulnerability in n/a, published on 23 Aug 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

AccuPOS 2017.8 is installed with the insecure "Authenticated Users: Modify" permission for files within the installation path. This may allow local attackers to compromise the integrity of critical resource and executable files.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2018-15809?

It affects 1 product.


Products: Accupos Accupos.

## How do I fix CVE-2018-15809?

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

## Is CVE-2018-15809 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-15809 and fix it if it is affected.

What it is: CVE-2018-15809 is a medium-severity vulnerability in n/a, published on 23 Aug 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-15809 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-2018-15809/ (Markdown: https://insights.sbomify.com/CVE-2018-15809/index.md)
```

## Sources

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

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