CVE-2022-25510 — freetakserver
HIGHCVE-2022-25510 is a high-severity (CVSS 8.8) Hard-coded Credentials vulnerability in freetakserver. 1 public exploit reference exists, so weaponization risk is real. A fix is available for freetakserver — see the affected versions and patch details below.
Hard coded credentials in FreeTAKServer
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2022-25510 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
freetakserverReal-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
FreeTAKServer 1.9.8 contains a hardcoded Flask secret key which allows attackers to create crafted cookies to bypass authentication or escalate privileges.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | freetakserver | all versions | 1.9.8.5pip install --upgrade 'freetakserver==1.9.8.5' |
Affected Products
freetakserver-uifreetakserver-ui_projectResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for freetakserver, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update freetakserver to 1.9.8.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-25510 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2022-25510 in your dependencies?
Find it across PyPI, including transitive dependencies.