# CVE-2018-16207: Missing authorization in PowerAct Pro Master Agent for Windows

> Authenticated attackers can bypass access restrictions to alter or edit unauthorized files in PowerAct Pro Master Agent for Windows.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Mar 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-wvqh-764v-vx55

## What is CVE-2018-16207?

CVE-2018-16207 is a medium-severity missing authorization vulnerability in OMRON SOCIAL SOLUTIONS Co.,Ltd. PowerAct Pro Master Agent for Windows, published on 27 Mar 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

PowerAct Pro Master Agent for Windows Version 5.13 and earlier allows authenticated attackers to bypass access restriction to alter or edit unauthorized files via unspecified vectors.

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

It affects 1 product.


Products: Omron Poweract Pro Master Agent.

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

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

## Is CVE-2018-16207 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-16207 is a medium-severity missing authorization vulnerability in OMRON SOCIAL SOLUTIONS Co.,Ltd. PowerAct Pro Master Agent for Windows, published on 27 Mar 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-16207 in the wild and no public exploit code.

Affected product: OMRON SOCIAL SOLUTIONS Co.,Ltd. PowerAct Pro Master Agent for Windows. 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-16207/ (Markdown: https://insights.sbomify.com/CVE-2018-16207/index.md)
```

## Sources

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

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