CVE-2020-19278 json
Phachon mm-wiki Cross Site Request Forgery vulnerability
published 3y ago modified 4mo ago also GHSA-f6xp-59jq-r35c , EUVD-2023-1280
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 42%
- public exploits
- 0
- none known
Summary
Cross Site Request Forgery vulnerability found in Phachon mm-wiki v.0.1.2 allows a remote attacker to execute arbitrary code via the system/user/save parameter.
Is CVE-2020-19278 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.50% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/phachon/mm-wiki/issues/68 referenced PoC, tagged "exploit" by a source, unverified
- imgur.com https://imgur.com/EABvnwz referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/phachon/mm-wiki | <=0.1.2 |
no fix listed |
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
github.com
/phachon/mm-wiki/issues/68
web, exploit, issue-tracking, third-party-advisory
-
imgur.com
/EABvnwz
web, exploit
-
nvd.nist.gov
/vuln/detail/CVE-2020-19278
advisory
-
github.com
/phachon/mm-wiki
package
Sources
- CVE List CVE-2020-19278
- GitHub Advisory GHSA-f6xp-59jq-r35c
- NVD CVE-2020-19278
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.