# CVE-2016-15002: MONyog Ultimate Cookie privileges management

> Attackers can escalate privileges by manipulating cookie parameters in MONyog Ultimate, gaining unauthorized administrative access.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jun 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-64vp-q339-g7h5

## What is CVE-2016-15002?

CVE-2016-15002 is a high-severity vulnerability in unspecified MONyog Ultimate, published on 9 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, was found in MONyog Ultimate 6.63. This affects an unknown part of the component Cookie Handler. The manipulation of the argument HasServerEdit/IsAdmin leads to privilege escalation. It is possible to initiate the attack remotely.

Weakness: CWE-565 (Reliance on Cookies without Validation and Integrity Checking), CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2016-15002?

It affects 1 product.


Products: Ideracorp Webyog Monyog Ultimate.

## How do I fix CVE-2016-15002?

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

## Is CVE-2016-15002 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-15002 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-15002 and fix it if it is affected.

What it is: CVE-2016-15002 is a high-severity vulnerability in unspecified MONyog Ultimate, published on 9 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-15002 exists.

Affected product: unspecified MONyog Ultimate. 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-2016-15002/ (Markdown: https://insights.sbomify.com/CVE-2016-15002/index.md)
```

## Sources

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

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