ExploitDBSighting
A client that retrieves vulnerability observations from Exploit-DB and pushes them to a Vulnerability-Lookup instance.
Exploit-DB.com is a comprehensive and publicly accessible database of security vulnerabilities and exploits, maintained by Offensive Security. It serves as a crucial resource for penetration testers, researchers, and ethical hackers by offering detailed information and proof-of-concept code.
Within the Vulnerability-Lookup project, data from Exploit-DB are leveraged as sightings
of type published-proof-of-concept, dated with the exploit's publication date. An
Exploit-DB entry shows that exploit code for the vulnerability is public; it is not an
observation of the vulnerability being exploited, which is what the exploited type
records ("This vulnerability was exploited and seen by the user reporting the sighting").
More information about the sightings:
Installation
pipx is an easy way to install and run Python applications in isolated environments. It's easy to install.
$ pipx install ExploitDBSighting
$ export ExploitDBSighting_CONFIG=~/conf.py
The configuration should be defined in a Python file (e.g., ~/.conf.py).
You must then set an environment variable (ExploitDBSighting_CONFIG) with the full path to this file.
With Docker
git clone https://github.com/vulnerability-lookup/ExploitDBSighting
cd ExploitDBSighting
# Make sure conf.py exists in the project root before running
docker compose up --build
Usage
Publishing sightings to Vulnerability-Lookup
$ ExploitDBSighting
CVE-2017-14084
https://www.exploit-db.com/exploits/42891
2017-09-28 00:00:00+00:00
Pushing sighting to Vulnerability-Lookup…
CVE-2017-14085
https://www.exploit-db.com/exploits/42893
2017-09-28 00:00:00+00:00
Pushing sighting to Vulnerability-Lookup…
CVE-2017-14086
https://www.exploit-db.com/exploits/42892
2017-09-28 00:00:00+00:00
Pushing sighting to Vulnerability-Lookup…
By specifying a date with the --since parameter:
$ ExploitDBSighting --since 2025-01-01
Fetching records starting at 0…
CVE-2025-48932
https://www.exploit-db.com/exploits/52383
2025-07-28 00:00:00+00:00
Pushing sighting to Vulnerability-Lookup…
CVE-2025-1974
https://www.exploit-db.com/exploits/52338
2025-06-20 00:00:00+00:00
Pushing sighting to Vulnerability-Lookup…
CVE-2025-0868
https://www.exploit-db.com/exploits/52145
2025-04-09 00:00:00+00:00
Pushing sighting to Vulnerability-Lookup…
Encountered record older than specified --since date (2025-01-01 00:00:00+00:00). Stopping.
By default, all CVE-tagged exploits are imported. Exploit-DB verifies only a small
fraction of recent submissions, so filtering on verified exploits misses most of them.
To import only verified exploits anyway, use --verified-only:
$ ExploitDBSighting --since 2025-01-01 --verified-only
License
ExploitDBSighting is licensed under GNU General Public License version 3
Copyright (c) 2024-2025 Computer Incident Response Center Luxembourg (CIRCL)
Copyright (C) 2024-2025 Cédric Bonhomme - https://github.com/cedricbonhomme
Metadata
Release files for ExploitDBSighting 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| exploitdbsighting-0.3.0.tar.gz | 17.3 kB | With provenance | Details for exploitdbsighting-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| exploitdbsighting-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for exploitdbsighting-0.3.0-py3-none-any.whl |
Total release size: 36.2 kB
Release files / exploitdbsighting-0.3.0.tar.gz
| Download URL | exploitdbsighting-0.3.0.tar.gz |
|---|---|
| Size | 17.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0552b1a3c1edd82a38a711212beaccf07454680c55ab3bf001b4abfcc2d4ed01
|
|
BLAKE2b-256 checksum How to use checksums |
2c2e1d85391d0ea0b2b2ad2195f4fc67281507eaa669c6914351176e44275820
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.
Transparency logRelease files / exploitdbsighting-0.3.0-py3-none-any.whl
| Download URL | exploitdbsighting-0.3.0-py3-none-any.whl |
|---|---|
| Size | 18.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f6147a34557b93355935f3f66a8888f5a44e83e52176583259ead045ad57c07e
|
|
BLAKE2b-256 checksum How to use checksums |
0b866696c082bb673fd94220bc7faadb7b7d55be492cb54e239dcdc691d10c15
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.
Transparency logSecurity for ExploitDBSighting 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for exploitdbsighting-0.3.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.