Lucene search
+L

5398 matches found

Kitploit
Kitploit
•added 2026/11/07 7:19 p.m.•614 views

mongoaudit

mongoaudit is a CLI tool for auditing MongoDB servers, detecting poor security settings and performing automated penetration testing. Installing Clone this repository and run the setup: git clone https://github.com/stampery/mongoaudit.git cd mongoaudit python setup.py install mongoaudit...

8.1CVSS7.1AI score0.10112EPSS
SaveExploits6References2
Kitploit
Kitploit
•added 2026/11/07 6:44 p.m.•106 views

heaphopper

heaphopper HeapHopper is a bounded model checking framework for Heap-implementations. Overview Setup sudo apt update && sudo apt install build-essential python3-dev virtualenvwrapper git clone https://github.com/angr/heaphopper.git && cd ./heaphopper mkvirtualenv -ppython3 heaphopper pip install ...

6AI score
SaveExploits0References1
CVE
CVE
•added 2026/11/07 6:00 a.m.•14 views

CVE-2026-118529

The Directorist: AI-Powered Business Directory, Listings & Classified Ads WordPress plugin, in versions before 8.11 , contains an incorrect authorization vulnerability (CWE-863). The plugin fails to verify if a user owns a specific listing before processing a featured-listing checkout . This allo...

3.1CVSS5.9AI score0.00142EPSS
SaveExploits0References1
Patchstack
Patchstack
•added 2026/11/07 6:00 a.m.•4 views

WordPress Directorist: AI-Powered Business Directory, Listings & Classified Ads plugin < 8.11 - Subscriber+ Other Users' Pending Listing Publication vulnerability

Subscriber+ Other Users' Pending Listing Publication vulnerability discovered by GivMeInJ in WordPress Plugin Directorist versions 8.11...

3.1CVSS5.8AI score0.00142EPSS
SaveExploits0References1Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/05 6:34 a.m.•11 views

Malicious code in quiche-tea-curut (npm)

Part of a self-republishing campaign: the package ships autopublish2.js, which in a loop gives the package a new random name, bumps its version, rewrites package.json and runs npm publish to publish the package again under the new name. Self-replicating publication is the propagation step of a...

6AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/05 6:34 a.m.•13 views

Malicious code in dependent-final (npm)

Part of a self-republishing campaign: the package ships test.js, which in a loop gives the package a new random name, bumps its version, rewrites package.json and runs npm publish to publish the package again under the new name. Self-replicating publication is the propagation step of a registry...

6AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/05 6:34 a.m.•11 views

Malicious code in wet_rat_replicate_automation (npm)

Part of a self-republishing campaign: the package ships autopublish2.js, which in a loop gives the package a new random name, bumps its version, rewrites package.json and runs npm publish to publish the package again under the new name. Self-replicating publication is the propagation step of a...

6AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/05 6:34 a.m.•12 views

Malicious code in unemployed_xerinae-toolteadev (npm)

Part of a self-republishing campaign: the package ships auto.js, which in a loop gives the package a new random name, rewrites package.json and runs npm publish to publish the package again under the new name. Self-replicating publication is the propagation step of a registry worm and fills the...

6AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/05 6:34 a.m.•13 views

Malicious code in related_blackbird-toolteadev (npm)

Part of a self-republishing campaign: the package ships auto.js, which in a loop gives the package a new random name, rewrites package.json and runs npm publish to publish the package again under the new name. Self-replicating publication is the propagation step of a registry worm and fills the...

6AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/05 6:34 a.m.•10 views

Malicious code in low_hummingbird_replicate_automation (npm)

Part of a self-republishing campaign: the package ships autopublish3.js, which in a loop gives the package a new random name, bumps its version, rewrites package.json and runs npm publish to publish the package again under the new name. Self-replicating publication is the propagation step of a...

6AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/05 6:34 a.m.•9 views

Malicious code in maila-talijah-alpha-128 (npm)

Part of a self-republishing campaign: the package ships loop.js, which in a loop gives the package a new random name, bumps its version, rewrites package.json and runs npm publish to publish the package again under the new name. Self-replicating publication is the propagation step of a registry...

6AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/05 6:34 a.m.•9 views

Malicious code in peas-tea-curut (npm)

Part of a self-republishing campaign: the package ships autopublish2.js, which in a loop gives the package a new random name, bumps its version, rewrites package.json and runs npm publish to publish the package again under the new name. Self-replicating publication is the propagation step of a...

6AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/04 9:32 a.m.•9 views

Malicious code in temporary_smelt_lavender-81 (npm)

Part of a self-republishing campaign: generated names of the form -, each package shipping the same autopublish.js, which runs npm publish --access public to publish the package again. Self-replicating publication is the propagation step of a registry worm and fills the registry with copies...

5.9AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/04 9:32 a.m.•11 views

Malicious code in intimate_ostrich_amethyst-45 (npm)

Part of a self-republishing campaign: generated names of the form -, each package shipping the same autopublish.js, which runs npm publish --access public to publish the package again. Self-replicating publication is the propagation step of a registry worm and fills the registry with copies...

5.9AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/04 9:32 a.m.•10 views

Malicious code in valid_antlion_amber-50 (npm)

Part of a self-republishing campaign: generated names of the form -, each package shipping the same autopublish.js, which runs npm publish --access public to publish the package again. Self-replicating publication is the propagation step of a registry worm and fills the registry with copies...

5.9AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/04 9:32 a.m.•14 views

Malicious code in itchy_gecko_magenta-98 (npm)

Part of a self-republishing campaign: generated names of the form -, each package shipping the same autopublish.js, which runs npm publish --access public to publish the package again. Self-replicating publication is the propagation step of a registry worm and fills the registry with copies...

5.9AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/04 9:32 a.m.•13 views

Malicious code in unfortunate_crawdad_emerald-79 (npm)

Part of a self-republishing campaign: generated names of the form -, each package shipping the same autopublish.js, which runs npm publish --access public to publish the package again. Self-replicating publication is the propagation step of a registry worm and fills the registry with copies...

5.9AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/04 9:32 a.m.•9 views

Malicious code in pure_opossum_amaranth-54 (npm)

Part of a self-republishing campaign: generated names of the form -, each package shipping the same autopublish.js, which runs npm publish --access public to publish the package again. Self-replicating publication is the propagation step of a registry worm and fills the registry with copies...

5.9AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/04 9:32 a.m.•9 views

Malicious code in xenacious_kangaroo_blush-47 (npm)

Part of a self-republishing campaign: generated names of the form -, each package shipping the same autopublish.js, which runs npm publish --access public to publish the package again. Self-replicating publication is the propagation step of a registry worm and fills the registry with copies...

5.9AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/04 9:32 a.m.•9 views

Malicious code in smooth_angelfish_emerald-54 (npm)

Part of a self-republishing campaign: generated names of the form -, each package shipping the same autopublish.js, which runs npm publish --access public to publish the package again. Self-replicating publication is the propagation step of a registry worm and fills the registry with copies...

5.9AI score
SaveExploits0References2Affected Software1
Rows per page
Query Builder