GHSA-2c7w-v459-cwgf is a high-severity (CVSS 7.5) CWE-1188 vulnerability in motioneye. 1 public exploit reference exists, so weaponization risk is real. A fix is available for motioneye — see the affected versions and patch details below.
MotionEye allows attackers to access sensitive information
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
GHSA-2c7w-v459-cwgf 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,166 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
motioneyeReal-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
MotionEye v0.42.1 and below allows attackers to access sensitive information via a GET request to /config/list. To exploit this vulnerability, a regular user password must be unconfigured.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | motioneye | all versions | 0.43.1b1pip install --upgrade 'motioneye==0.43.1b1' |
Research 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 motioneye, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update motioneye to 0.43.1b1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2c7w-v459-cwgf 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 GHSA-2c7w-v459-cwgf can be triaged on real exposure rather than presence alone.
Tailored to GHSA-2c7w-v459-cwgf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
How to detect GHSA-2c7w-v459-cwgf
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id ghsa-2c7w-v459-cwgf -u https://target- Template
- MotionEye Config Info Disclosure
- Severity
- high
- Impact
- Unauthenticated attackers can access sensitive MotionEye configuration data including upload passwords and network passwords through the /config/list endpoint when regular user authentication is not configured, potentially compromising camera systems and network access.
- Remediation
- Update MotionEye to version 0.42.2 or later and ensure regular user passwords are properly configured to restrict access.
Template by ProjectDiscovery nuclei-templates (DhiyaneshDK), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is GHSA-2c7w-v459-cwgf in your dependencies?
O3 Security finds GHSA-2c7w-v459-cwgf across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.