# CVE-2025-25968: Missing authorization in n/a

> An editor can access sensitive admin credentials via improper access control, leading to account takeover and privilege escalation.

- **Severity:** Medium 6.0 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Feb 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-4fg5-759r-24x3

## What is CVE-2025-25968?

CVE-2025-25968 is a medium-severity missing authorization vulnerability in n/a, published on 20 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

DDSN Interactive cm3 Acora CMS version 10.1.1 contains an improper access control vulnerability. An editor-privileged user can access sensitive information, such as system administrator credentials, by force browsing the endpoint and exploiting the 'file' parameter. By referencing specific files (e.g., cm3.xml), attackers can bypass access controls, leading to account takeover and potential privilege escalation.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Ddsn Cm3 Acora Content Management System.

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

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

## Is CVE-2025-25968 being exploited?

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

Public exploit code:

- https://github.com/padayali-JD/CVE-2025-25968 (github_poc): https://github.com/padayali-JD/CVE-2025-25968

## Other vulnerabilities in n/a

- [CVE-2025-22964](https://insights.sbomify.com/CVE-2025-22964/): SQL injection in n/a (high 8.1)
- [CVE-2013-4726](https://insights.sbomify.com/CVE-2013-4726/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2013-4723](https://insights.sbomify.com/CVE-2013-4723/): Open redirect in n/a (medium 5.8)
- [CVE-2013-4724](https://insights.sbomify.com/CVE-2013-4724/): Information disclosure in n/a (medium 5.0)
- [CVE-2013-4725](https://insights.sbomify.com/CVE-2013-4725/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-25968 is a medium-severity missing authorization vulnerability in n/a, published on 20 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-25968 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-25968/ (Markdown: https://insights.sbomify.com/CVE-2025-25968/index.md)
```

## Sources

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

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