Information Disclosure · payload topic
Insecure Source Code Management
24 passages · 16 code blocks
Out of date: the sync last ran 5 hours ago. Newer CVEs and scores may be missing from the map.
Every mark is a titled passage of this topic's pages, in reading order; the brighter ones carry code. For testing systems you own or are authorised to test, and for defending them. Nothing here is run by this page.
Open Insecure Source Code Management on GitHubInsecure Source Code Management (SCM) can lead to several critical vulnerabilities in web applications and services. Developers often rely on SCM systems like Git and Subversion (SVN) to manage their source code versions. However, poor security practices, such as leaving .git and .svn folders in pr…
Source: PayloadsAllTheThings. From PayloadsAllTheThings by Swissky and contributors. MIT License, Copyright (c) 2019 Swissky.
Every one of the 24 is a mark on the map. Named now: 1 to 24, reading order first.
- Insecure Source Code Management
- Methodology
- Bazaar: Bazaar
- Bazaar: rip-bzr.pl
- Bazaar: bzrdumper
- Git: Methodology
- Git: Recovering file contents from .git/logs/HEAD
- Git: Recovering file contents from .git/index
- Git: git-dumper.py
- Git: diggit.py
- Git: GoGitDumper
- Git: rip-git
- Git: GitHack
- Git: GitTools
- Git: noseyparker
- Git: trufflehog
- Git: Yar
- Git: Gitrob
- Git: Gitleaks
- Mercurial: Mercurial
- Mercurial: rip-hg.pl
- Subversion: Subversion
- Subversion: Tools
- Subversion: Methodology
Zoom in on the map and the dots under the middle of it are named where they are.
Data as of 2026-11-14. CVE List through 2026-11-14 · EPSS of 2026-11-13 · CISA KEV checked 2026-11-14. Source: PayloadsAllTheThings by Swissky and contributors, MIT License. For authorised testing only.