pysec-2020-74
Vulnerability from pysec
Published
2020-12-02 08:15
Modified
2020-12-02 16:29
Details
Multiple cross-site scripting (XSS) vulnerabilities in Papermerge before 1.5.2 allow remote attackers to inject arbitrary web script or HTML via the rename, tag, upload, or create folder function. The payload can be in a folder, a tag, or a document's filename. If email consumption is configured in Papermerge, a malicious document can be sent by email and is automatically uploaded into the Papermerge web application. Therefore, no authentication is required to exploit XSS if email consumption is configured. Otherwise authentication is required.
Impacted products
| Name | purl | papermerge | pkg:pypi/papermerge |
|---|
Aliases
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "papermerge",
"purl": "pkg:pypi/papermerge"
},
"ranges": [
{
"events": [
{
"introduced": "1.2.0"
},
{
"fixed": "1.5.2"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.2.0",
"1.3.0"
]
}
],
"aliases": [
"CVE-2020-29456",
"GHSA-9w49-m7xh-5r39"
],
"details": "Multiple cross-site scripting (XSS) vulnerabilities in Papermerge before 1.5.2 allow remote attackers to inject arbitrary web script or HTML via the rename, tag, upload, or create folder function. The payload can be in a folder, a tag, or a document\u0027s filename. If email consumption is configured in Papermerge, a malicious document can be sent by email and is automatically uploaded into the Papermerge web application. Therefore, no authentication is required to exploit XSS if email consumption is configured. Otherwise authentication is required.",
"id": "PYSEC-2020-74",
"modified": "2020-12-02T16:29:00Z",
"published": "2020-12-02T08:15:00Z",
"references": [
{
"type": "REPORT",
"url": "https://github.com/ciur/papermerge/issues/228"
},
{
"type": "WEB",
"url": "https://www.papermerge.com/"
},
{
"type": "WEB",
"url": "https://github.com/ciur/papermerge/releases/tag/v1.5.2"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-9w49-m7xh-5r39"
}
]
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…