CVE-2025-23044 Details
Description
PwnDoc is a penetration test report generator. There is no CSRF protection in pwndoc, allowing attackers to send requests on a logged-in user's behalf. This includes GET and POST requests due to the missing SameSite= attribute on cookies and the ability to refresh cookies. Commit 14acb704891245bf1703ce6296d62112e85aa995 patches the issue.
A Cross-Site Request Forgery (CSRF) vulnerability has been identified in PwnDoc, a penetration test report generator. The issue arises from the lack of CSRF protection, enabling attackers to send requests on behalf of logged-in users. This vulnerability affects both GET and POST requests, due to the absence of the SameSite attribute on cookies and the ability to refresh cookies. Exploitation can lead to unauthorized actions, such as creating admin accounts.
Users can update to the latest version of PwnDoc, where this vulnerability has been patched.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jan 21, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/pwndoc/pwndoc/commit/14acb704891245bf1703ce6296d62112e85aa995 | [email protected] | Patch |
| https://github.com/pwndoc/pwndoc/security/advisories/GHSA-9v2v-jxvw-52rq | [email protected] | ExploitVendor Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-352 | Cross-Site Request Forgery (CSRF) | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| pwndoc project pwndoc | < 0.9.0 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| May 7, 2025 | Initial Analysis | [email protected] |
| Jan 20, 2025 | New CVE Received | [email protected] |