{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-27413 exists.","fix":"No fix has been published for CVE-2025-27413 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-27413 is a medium-severity path traversal vulnerability in pwndoc, published on 28 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-27413 and fix it if it is affected.\n\nWhat it is: CVE-2025-27413 is a medium-severity path traversal vulnerability in pwndoc, published on 28 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-27413 exists.\n\nAffected product: pwndoc. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-27413/ (Markdown: https://insights.sbomify.com/CVE-2025-27413/index.md)","id":"CVE-2025-27413","markdown":"https://insights.sbomify.com/CVE-2025-27413/index.md","name":"CVE-2025-27413","record":{"aliases":["GHSA-r3vj-47cf-4672"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"PwnDoc reporting app","requires_auth":"high_privilege","summary":"Administrators can exploit path traversal in backup restoration to write arbitrary files, potentially overwriting source code to achieve remote code execution.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"pwndoc","vendor":"pwndoc_project"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"PwnDoc is a penetration test reporting application. Prior to version 1.2.0, the backup restore functionality allows an administrator to import raw data into the database, including Path Traversal (`../`) sequences. This is problematic for the template update functionality as it uses the path from the database to write arbitrary content to, potentially overwriting source code to achieve Remote Code Execution. Any user with the `backups:create`, `backups:update` and `templates:update` permissions (only administrators by default) can write arbitrary content to anywhere on the filesystem. By overwriting source code, it is possible to achieve Remote Code Execution. Version 1.2.0 fixes the issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"PwnDoc Arbitrary File Write to RCE using Path Traversal in template update from backup templates.json","id":"CVE-2025-27413","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2025"},"n_packages":0,"n_references":6,"next":{"headline":"MinIO SFTP authentication bypass due to improperly trusted SSH key","id":"CVE-2025-27414"},"packages":[],"prev":{"headline":"REDAXO allows Authenticated Reflected Cross Site Scripting - packages installation","id":"CVE-2025-27412"},"products":["pwndoc"],"published":"2025-02-28","related":[{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2022-45771","kev_date_added":null,"published":"2022-12-05"},{"cvss_score":8.8,"headline":"Auth bypass in n/a","id":"CVE-2021-31590","kev_date_added":null,"published":"2021-07-19"},{"cvss_score":7.6,"headline":"PenDoc vulnerable to Arbitrary File Read on updating and downloading templates using Path Traversal","id":"CVE-2024-55602","kev_date_added":null,"published":"2024-12-10"},{"cvss_score":6.8,"headline":"Cross-Site Request Forgery (CSRF) allows creating admin account with POST request","id":"CVE-2025-23044","kev_date_added":null,"published":"2025-01-20"},{"cvss_score":6.5,"headline":"PwnDoc Arbitrary File Write to RCE using Path Traversal in backup restore as admin","id":"CVE-2025-27410","kev_date_added":null,"published":"2025-02-28"},{"cvss_score":6.5,"headline":"pwndoc's UnhandledPromiseRejection on audits causes Denial of Service (DoS)","id":"CVE-2024-55653","kev_date_added":null,"published":"2024-12-10"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-03-04","vendors":["pwndoc"]},"summary":"Administrators can exploit path traversal in backup restoration to write arbitrary files, potentially overwriting source code to achieve remote code execution.","url":"https://insights.sbomify.com/CVE-2025-27413/"}