CVE-2025-25617 Privilege escalation in n/a
Medium 4.3
Published
Updated
Check this codebase for CVE-2025-25617 and fix it if it is affected.
What it is: CVE-2025-25617 is a medium-severity vulnerability in n/a, published on 7 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25617 exists.
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-25617/ (Markdown: https://insights.sbomify.com/CVE-2025-25617/index.md)
Teachers can improperly create syllabus content due to incorrect access control, leading to privilege escalation in Unifiedtransform.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-25617?
CVE-2025-25617 is a medium-severity vulnerability in n/a, published on 7 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Incorrect Access Control in Unifiedtransform 2.X leads to Privilege Escalation allowing teachers to create syllabus.
Weakness: CWE-284
Which versions are affected by CVE-2025-25617?
How do I fix CVE-2025-25617?
No fix has been published for CVE-2025-25617 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-25617 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25617 exists.
Public exploit code: 1 proofs of concept on GitHub.
Sources
Also known as GHSA-3243-w5fh-rcj8.