# CVE-2026-59501: Priority – CWE-284: Improper Access Control

> Attackers can bypass access controls in the Priority Portal Generator addon for Priority ERP by lacking Priwall v3 protection.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/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:** 13 Aug 2026
- **Updated:** 24 Aug 2026
- **Also known as:** GHSA-6jj4-v58m-mhvw

## What is CVE-2026-59501?

CVE-2026-59501 is a high-severity missing authorization vulnerability in Portal Generator addon to Priority ERP (developed by Soft Solutions), published on 13 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

: Improper Access Control vulnerability in Priority Portal Generator addon to Priority ERP (developed by Soft Solutions).

This issue affects Portal Generator addon to Priority ERP (developed by Soft Solutions): All versions without Priwall v3.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-59501?


## How do I fix CVE-2026-59501?

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

## Is CVE-2026-59501 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-59501 and fix it if it is affected.

What it is: CVE-2026-59501 is a high-severity missing authorization vulnerability in Portal Generator addon to Priority ERP (developed by Soft Solutions), published on 13 Aug 2026. 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-2026-59501 in the wild and no public exploit code.

Affected product: Portal Generator addon to Priority ERP (developed by Soft Solutions). 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-2026-59501/ (Markdown: https://insights.sbomify.com/CVE-2026-59501/index.md)
```

## Sources

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

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