# CVE-2025-31513: Privilege escalation in n/a

> Attackers can elevate to administrator privileges by manipulating the IsAdminApprover parameter in the requestSubmit API call.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 22 Jul 2025
- **Updated:** 18 Aug 2025
- **Also known as:** GHSA-69qv-v93w-qxcp

## What is CVE-2025-31513?

CVE-2025-31513 is a medium-severity vulnerability in n/a, published on 22 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in AlertEnterprise Guardian 4.1.14.2.2.1. One can elevate to administrator privileges via the IsAdminApprover parameter in a Request%20Building%20Access requestSubmit API call. The vendor has stated that the system is protected by updating to a version equal to or greater than one of the following build numbers: 4.1.12.2.1.19, 4.1.12.5.2.36, 4.1.13.0.60, 4.1.13.2.0.3.39, 4.1.13.2.0.3.41, 4.1.13.2.42, 4.1.13.2.25.44, 4.1.14.0.13, 4.1.14.0.43, 4.1.14.0.48, and 4.1.14.1.5.32.

Weakness: CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2025-31513?


## How do I fix CVE-2025-31513?

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

## Is CVE-2025-31513 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-31513 and fix it if it is affected.

What it is: CVE-2025-31513 is a medium-severity vulnerability in n/a, published on 22 Jul 2025. 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-2025-31513 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-2025-31513/ (Markdown: https://insights.sbomify.com/CVE-2025-31513/index.md)
```

## Sources

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

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