CVE-2025-14692 — mayan-edms
MEDIUMCVE-2025-14692 is a medium-severity (CVSS 4.3) Open Redirect vulnerability in mayan-edms. A fix is available for mayan-edms — see the affected versions and patch details below.
Mayan EDMS has an Open Redirect through the /authentication/ file
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-14692.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2025-14692 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
mayan-edms🐍mayan-edms🐍mayan-edms🐍mayan-edms🐍mayan-edmsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
A flaw has been found in Mayan EDMS up to 4.10.1. The impacted element is an unknown function of the file /authentication/. This manipulation causes open redirect. It is possible to initiate the attack remotely. The exploit has been published and may be used. Upgrading to version 4.10.2 is sufficient to resolve this issue. The affected component should be upgraded. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | mayan-edms | ≥ 4.10.0&&< 4.10.2 | 4.10.2pip install --upgrade 'mayan-edms==4.10.2' |
| 🐍PyPI | mayan-edms | ≥ 4.9.0&&< 4.9.7 | 4.9.7pip install --upgrade 'mayan-edms==4.9.7' |
| 🐍PyPI | mayan-edms | ≥ 4.8.0&&< 4.8.10 | 4.8.10pip install --upgrade 'mayan-edms==4.8.10' |
| 🐍PyPI | mayan-edms | ≥ 4.7.0&&< 4.7.8 | 4.7.8pip install --upgrade 'mayan-edms==4.7.8' |
| 🐍PyPI | mayan-edms | all versions | 4.6.12pip install --upgrade 'mayan-edms==4.6.12' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mayan-edms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update mayan-edms to 4.10.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-14692 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-14692 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-14692. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-14692 in your dependencies?
O3 Security finds CVE-2025-14692 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.