Skip to main content
Mallory
CriticalExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2018-7600: Drupalgeddon2

Published Mar 29, 2018 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS100.0%100th percentile
CISA KEVYesAdded Nov 3, 2021
In the wildActivePer CISA KEV
Vendors
Debian ProjectDrupal
IdentifiersCVE-2018-7600CWE-20 · Improper Input Validation

Drupalgeddon2 is an unauthenticated remote code execution vulnerability in Drupal core affecting multiple subsystems under default or common module configurations. Affected releases include Drupal before 7.58, 8.x before 8.3.9, 8.4.x before 8.4.6, and 8.5.x before 8.5.1. Improper input validation allows crafted requests to trigger arbitrary code execution through the Form API render array, including AJAX form processing. Executed code runs with the privileges of the web server process and can compromise the Drupal site.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation permits arbitrary code execution with web server process privileges, website compromise, and modification or deletion of website files and CMS data. Observed exploitation has installed cryptocurrency miners and botnet components and used compromised servers to launch DDoS attacks. Exploitation does not require authentication.

Mitigation

If you can’t patch tonight, do this now.

No specific validated workaround is available. Until upgrades can be applied, limit public access to affected Drupal installations. Investigate exposed servers for evidence of compromise and initiate incident response and recovery where necessary; access restrictions and patching alone do not eradicate an existing compromise.

Remediation

Patch, then assume compromise.

Upgrade Drupal core to a supported, patched release. Historical fixes for this vulnerability are Drupal 7.58, 8.3.9, 8.4.6, and 8.5.1 for their respective branches. CVE-2018-7602 is a separate, related vulnerability requiring its own patches; applying only the CVE-2018-7600 fix does not address it. Investigate previously exposed installations for compromise, because upgrading does not remove existing malware or unauthorized modifications. Historical Drupal guidance treated sites not updated by April 11, 2018, as potentially compromised.

Public exploits

Exploits

30 exploits validated by Mallory's analysis. Hidden: 10 rejected by Mallory's analysis as not a working exploit; 4 not yet analyzed, such as Exploit-DB entries. Showing the 25 most capable, earliest first.

View more in app →
drupal_drupalgeddon2.rbThis repository contains a single Metasploit module implementing the 'Drupalgeddon 2' exploit (CVE-2018-7600), targeting a critical remote code execution vulnerability in Drupal's Forms API. The exploit leverages property injection via crafted HTTP requests to vulnerable Drupal endpoints, allowing arbitrary code execution as the web server user. The module supports multiple payload types (PHP, command, native) and targets Drupal versions 6.x, <7.58, 8.2.x, <8.3.9, <8.4.6, and <8.5.1. The main file, written in Ruby, is structured as a standard Metasploit exploit module and uses HTTP requests to endpoints such as '/user/password', '/file/ajax/name/#value/{form_build_id}', and '/user/register' to trigger the vulnerability. The module is weaponized, allowing attackers to easily select and deliver payloads for post-exploitation. No hardcoded IPs or domains are present; the attacker specifies the target Drupal site URL when running the module.Disclosed Mar 28, 2018 · Framework: metasploit · ruby · networkWeaponizedCVE-2018-7600-Drupal-RCEThis repository is a comprehensive collection of proof-of-concept and operational exploits for CVE-2018-7600, also known as Drupalgeddon2, a critical remote code execution vulnerability affecting Drupal versions prior to 7.58 and 8.x prior to 8.5.1. The repository contains 8 exploit scripts in various languages (Python, Ruby, Perl, Bash), each demonstrating different approaches to exploiting the vulnerability. The main attack vector is network-based, targeting the Drupal user registration endpoint with specially crafted POST requests that abuse form rendering parameters to achieve arbitrary PHP code execution. Several scripts support mass exploitation by reading lists of target URLs. The exploits can upload webshells (e.g., s.php, shell.php, payload.php) or execute arbitrary commands, providing attackers with persistent access or interactive shells. The repository is well-structured, with each script referencing its original source and intended Drupal version. The README provides a clear mapping of scripts to Drupal versions and sources. No detection-only scripts are present; all scripts are capable of exploitation. The repository is suitable for both proof-of-concept testing and operational exploitation.g0rx · Disclosed Mar 30, 2018 · python · ruby · networkOperationalDrupalgeddon2This repository contains two Ruby exploit scripts (drupalgeddon2.rb and drupalgeddon2-customizable-beta.rb) targeting the critical remote code execution vulnerability CVE-2018-7600 (Drupalgeddon2) in Drupal CMS. The exploit works against Drupal 7.x < 7.58, 8.x < 8.3.9, 8.4.x < 8.4.6, and 8.5.x < 8.5.1. The main script (drupalgeddon2.rb) automates detection of the Drupal version, attempts code execution via vulnerable form endpoints (/user/register for Drupal 8.x, /user/password for Drupal 7.x), and can either execute arbitrary commands or write a PHP web shell (shell.php) to the web root or writable subdirectories. The customizable version (drupalgeddon2-customizable-beta.rb) allows more granular control over the attack parameters, including the PHP method, form path, and Cloudflare bypass options. The README provides detailed usage instructions, example payloads, and troubleshooting tips. The exploit is operational and provides both direct command execution and persistent shell access if the target is writable. No detection-only scripts are present; both code files are full exploits.dreadlocked · Disclosed Apr 12, 2018 · ruby · networkOperationalCVE-2018-7600-Drupal-0day-RCEThis repository contains a Perl exploit script (drupal.pl) and a README.txt for CVE-2018-7600, a critical remote code execution vulnerability in Drupal CMS. The exploit works by sending a specially crafted POST request to the Drupal user registration endpoint, leveraging the vulnerability to execute arbitrary commands. The script attempts to download a PHP web shell from a remote GitHub URL and save it as shell.php on the target server, providing the attacker with remote code execution capabilities. The README provides basic usage instructions. The repository is straightforward, with the main exploit logic contained in drupal.pl, and is operational with a hardcoded payload (web shell).dr-iman · Disclosed Apr 14, 2018 · perl · networkOperationalCVE-2018-7600This repository contains a Python exploit script (Drupalgeddon2.py) targeting the Drupalgeddon 2 vulnerability (CVE-2018-7600) in Drupal CMS. The exploit works by sending a specially crafted HTTP POST request to the '/user/register' endpoint of a Drupal site, abusing the 'mail[#post_render][]' and 'mail[#markup]' parameters to trigger arbitrary command execution on the server. The script supports both testing for vulnerability (by echoing a string) and exploitation (by executing a user-supplied command). The repository also includes a README.md with usage instructions and a requirements.txt listing dependencies ('requests' and 'argparse'). The main entry point is Drupalgeddon2.py, which is a standalone operational exploit. No hardcoded IPs or domains are present; the target is specified by the user at runtime.sl4cky · Disclosed Apr 15, 2018 · python · networkOperationalCVE-2018-7600This repository contains two Python exploit scripts targeting critical remote code execution vulnerabilities in Drupal 7: CVE-2018-7600 (SA-CORE-2018-002) and CVE-2018-7602 (SA-CORE-2018-004). Both scripts leverage form poisoning and AJAX endpoints to achieve arbitrary command execution on vulnerable Drupal installations. - drupa7-CVE-2018-7600.py exploits the 'user/password' form and triggers code execution via the '/file/ajax' endpoint. It requires only the target URL and can execute arbitrary commands (default: 'id') using a specified PHP function (default: 'passthru'). - drupa7-CVE-2018-7602.py requires valid user credentials and targets the 'user_cancel_confirm_form', poisoning it via the 'destination' parameter and triggering execution through '/file/ajax/actions/cancel/#options/path/'. Both scripts support proxy configuration for traffic interception. The repository is well-structured, with a README providing usage instructions, requirements, and detailed explanations of the attack flow. The exploits are operational, providing real command execution on the target system, and are not part of a larger framework. The main attack vector is network-based, exploiting HTTP endpoints exposed by Drupal 7.pimps · Disclosed Apr 17, 2018 · python · networkOperationaldrupalgeddon2This repository contains a Python exploit script (drupalgeddon2.py) and a README.md file. The exploit targets CVE-2018-7600 (Drupalgeddon2), a critical remote code execution vulnerability in Drupal. The script allows an attacker to execute arbitrary OS commands on a vulnerable Drupal installation by sending specially crafted HTTP POST requests to the target's 'user/password' endpoint. The exploit works by abusing Drupal's form API to inject a 'passthru' function call, passing the attacker's command as a parameter. The script is run from the command line, requiring the attacker to specify the target URL (-h) and the command to execute (-c). The README provides usage instructions and an example. The only fingerprintable endpoint is the user-supplied target URL, exemplified as 'http://www.victim.com'. The code is operational and can be used directly to exploit vulnerable Drupal sites.lorddemon · Disclosed Apr 19, 2018 · python · networkOperationalCVE-2018-7600-Drupal-POC-EXPThis repository contains a Python exploit script (cve-2018-7600_cmd.py) targeting the Drupalgeddon 2 vulnerability (CVE-2018-7600) in Drupal CMS. The exploit leverages a flaw in Drupal's AJAX API to achieve remote code execution by sending a specially crafted POST request to the /user/register endpoint. The script provides an interactive shell-like interface, allowing the attacker to execute arbitrary system commands on the vulnerable server. The output of each command is written to /exphub.txt on the target, which can be accessed via HTTP. The exploit supports Drupal versions 6.x, 7.x < 7.58, 8.3 < 8.3.9, 8.4 < 8.4.6, and 8.5 < 8.5.1. The repository also includes a README with usage instructions and version information. No hardcoded IPs or domains are present; the target URL is supplied by the user at runtime.zhzyker · Disclosed Apr 7, 2020 · python · networkOperationaldrupalhunterThis repository contains a Python exploit script (0-day.py) targeting the Drupalgeddon2 vulnerability (CVE-2018-7600) in Drupal CMS. The exploit leverages a vulnerability in the Drupal form API to achieve unauthenticated remote code execution. The script takes a target URL (-h) and an OS command (-c) as arguments, crafts malicious POST requests to the 'user/password' and 'file/ajax/name/#value/' endpoints, and executes the supplied command on the target server. The repository includes a README referencing the CVE, a .gitignore for Drupal projects, and a GPLv3 license. The exploit is operational, providing direct command execution on vulnerable Drupal installations accessible over the network.ynsmroztas · Disclosed Jun 18, 2020 · python · networkOperationalDrupalgeddon2This repository contains a Python exploit script (drupalgeddon2.py) targeting CVE-2018-7600, also known as 'Drupalgeddon2', a critical remote code execution vulnerability in Drupal versions prior to 7.58, 8.3.9, 8.4.6, and 8.5.1. The exploit works by sending specially crafted POST requests to the /user/register endpoint, abusing the #post_render or #lazy_builder parameters to execute arbitrary PHP code on the server. If successful, the script uploads a PHP reverse shell to the web root of the Drupal installation and triggers it, granting the attacker a remote shell. The exploit is operational and automates the process of vulnerability checking, payload upload, and shell triggering. The repository includes a README with usage instructions and PoC details, a LICENSE file, and a .gitignore. The main exploit logic resides in drupalgeddon2.py, which is the only code file. The exploit is designed for Linux targets and requires the attacker to specify the target URL, local host, and port for the reverse shell connection.ruthvikvegunta · Disclosed Aug 10, 2020 · python · networkOperationalCVE-2018-7600This repository contains a Python exploit script (cve-2018-7600.py) targeting CVE-2018-7600, also known as Drupalgeddon 2. The exploit leverages a remote code execution vulnerability in Drupal versions 6.x, 7.x, and 8.x (prior to patch). The script allows an unauthenticated attacker to execute arbitrary system commands on a vulnerable Drupal server by abusing the form API and AJAX endpoints. The user provides the target URL, the command to execute, and optionally a PHP function and proxy. The script crafts specific HTTP POST requests to poison the form and then triggers code execution via a secondary AJAX request. The README.md file is a simple disclaimer. The exploit is operational, providing real command execution on the target, and is not a detection script. No hardcoded IPs or domains are present; the target is specified at runtime. The code is a modified version of a public exploit, with clear structure and user input handling.M-Abid34 · Disclosed Aug 4, 2025 · python · networkOperationalCVE-2018-7600This repository contains a working exploit for CVE-2018-7600 (Drupalgeddon2), targeting Drupal 7.x (including 7.56) and possibly early 8.x versions. The exploit is implemented in a single Python script ('drupal7.56-RCE.py') and is accompanied by a detailed README.md in Indonesian, which explains the vulnerability, usage, and mitigation steps. The exploit works by sending a specially crafted POST request to the 'user/password' endpoint of a vulnerable Drupal instance, injecting a payload that leverages the PHP 'passthru' function to execute arbitrary system commands. It then extracts a 'form_build_id' from the server's response and uses it in a second request to the 'file/ajax/name/#value/{form_build_id}' endpoint to trigger the actual command execution. The script is operational and allows the user to specify any command to be executed on the target server, returning the output. The attack vector is network-based, requiring only HTTP access to the vulnerable Drupal instance. No authentication is required. The repository is well-structured, with clear instructions and warnings about legal and ethical use.xxxTectationxxx · Disclosed Aug 12, 2025 · python · networkOperationalCVE-2018-7600This repository contains a Python3 exploit for CVE-2018-7600 (Drupalgeddon2), a critical unauthenticated remote code execution vulnerability in Drupal 7.x and 8.x (pre-patch). The repository consists of a README.md with usage instructions and a single exploit script (poc.py). The exploit works by sending a specially crafted POST request to the /user/register endpoint of a vulnerable Drupal instance, leveraging Drupal's AJAX form rendering to execute arbitrary system commands. The script sets up a reverse shell listener on the attacker's machine (0.0.0.0:1337) and, upon successful exploitation, spawns a fully interactive shell from the target back to the attacker using a Python-based reverse shell payload. The code is operational and provides a real shell if the target is vulnerable and reachable. The main entry point is poc.py, which requires the target URL and the attacker's listener IP as arguments.muhammedkayag · Disclosed Aug 12, 2025 · python · networkOperationalCVE-2018-7600This repository contains a Rust-based command-line exploit for CVE-2018-7600, a critical remote code execution vulnerability in Drupal 7 (<= 7.57). The exploit works in two stages: first, it poisons the Drupal form cache by sending a crafted POST request to the 'user/password' endpoint, injecting a renderable array with a #post_render callback set to an attacker-controlled PHP function (default: passthru) and #markup containing the command to execute. It then parses the response to extract the form_build_id and triggers the payload by POSTing to the 'file/ajax/name/#value/<form_build_id>' endpoint, causing the PHP function to execute the command on the server. The tool supports custom commands, PHP functions, and optional HTTP/S proxying. The code is contained in a single Rust file (src/main.rs) and is operational, providing real remote code execution if the target is vulnerable. No hardcoded endpoints are present; the user supplies the target URL. The exploit disables TLS certificate verification by default, allowing attacks against servers with invalid certificates.nika0x38 · Disclosed Sep 21, 2025 · rust · networkOperationalDrupalgeddon2-CVE-2018-7600Repository contains a single Python exploit script (bixi.py) plus README and MIT LICENSE. The code implements an operational, interactive-ish CLI exploit for CVE-2018-7600 (Drupalgeddon 2) aimed at Drupal (README claims Drupal 7). Exploitation is performed over the network via two HTTP POST requests: (1) POST to the Drupal password reset route (q=user/password) with crafted parameters name[#post_render][]=<injection_type> and name[#markup]=<command> to force Drupal to embed a command and return a form_build_id; (2) POST to the Drupal AJAX endpoint (q=file/ajax/name/#value/<form_build_id>) to trigger rendering and execute the command. The script supports multiple PHP execution primitives (system, passthru, exec, shell_exec), disables TLS verification, uses a fixed browser-like User-Agent, and prints command output by attempting to parse the response as JSON (Drupal AJAX responses are often JSON arrays). It also includes a keyword-to-command mapping for common Linux/Windows enumeration tasks (e.g., reading /etc/passwd, /etc/hosts, Windows hosts file, net user, systeminfo) and a 'test' keyword to validate execution. No persistence, reverse shell, or lateral movement is implemented—this is direct command execution with predefined recon commands.bixiPRO · Disclosed Feb 10, 2026 · python · markdown · networkOperationaldrupalgeddon2-cliThis repository is a small standalone Python exploit project for Drupalgeddon2 (CVE-2018-7600). It contains three files: a .gitignore, a detailed README, and a single executable Python script, drupalgeddon2.py. The code is not part of a larger exploit framework. The exploit targets the Drupal 8 unauthenticated Form API injection vector via the user registration AJAX endpoint. The script constructs a POST request to /user/register?element_parents=account/mail/%23value&ajax_form=1&_wrapper_format=drupal_ajax with crafted parameters such as mail[#post_render][]=exec and mail[#markup]=<command>, causing Drupal to execute attacker-controlled shell commands during render processing. Rather than only running a one-shot command, the script operationalizes the primitive by deploying a small PHP web shell. It base64-encodes the PHP shell locally, then uses the injected command execution to run a shell command on the server that decodes and writes the file using tee. The shell filename is randomized each run, and the GET parameter used to pass commands is also randomized using an MD5 of random bytes. After deployment, the script verifies success by requesting the shell URL and checking for a random echoed token. Capabilities include: unauthenticated remote code execution, persistent web shell deployment, one-off command execution, interactive pseudo-shell access, optional deploy-only mode, proxy support, TLS verification disabling, and configurable timeout/shell name/parameter. The interactive mode retrieves whoami and hostname first, then loops on operator input and relays commands through the planted shell. The exploit is operational rather than a bare PoC because it includes a working payload chain and reusable foothold, but it is still relatively simple and hardcoded to the Drupal 8 vector. It does not support the Drupal 7 exploitation path. No malicious destructive behavior or obvious fake-exploit indicators are present.nayem-m · Disclosed Jun 10, 2026 · python · markdown · web · networkOperationalCVE-2018-7600-PoCSAWPOC is a small standalone Python 3 exploit repository containing a README and sawpoc.py. The script targets Drupalgeddon2 (CVE-2018-7600), abusing Drupal Form API render/lazy-builder properties in crafted requests to invoke PHP functions with attacker-controlled commands. It supports Drupal 7 and Drupal 8 request formats, extracts a Drupal 7 form_build_id before its AJAX trigger request, supports optional authenticated sessions, optional proxying, verbose output, and an interactive command shell. Its hardcoded PHP payload can be base64-delivered as a shell.php webshell accepting commands through the c request parameter; otherwise the interactive loop repeatedly invokes the injection path. The README documents authorized research use, Python 3 and colorama requirements, and command-line invocation. This is functional exploitation code rather than a scanner, although success depends on target version, endpoint availability, and target-side permissions.elkhaoudari · Disclosed Aug 20, 2026 · python · markdown · web · networkOperationaledu-reconedu-recon is a Python 3.10+ reconnaissance, vulnerability-triage, and active assessment orchestrator aimed at education-sector engagements. It has 38 files, primarily Python modules, with `recon.py` as the CLI entry point and `run.sh` as a one-command launcher. Its stdlib web UI (`edurecon/webui.py`) exposes scan submission, live logs, findings, report/reproduction generation, and dump functions; it defaults to localhost but can be bound to all interfaces without authentication. The engine expands CIDRs through nmap ping sweeps and domains through subdomain enumeration, then concurrently runs Shodan enrichment, nmap service/version scanning, dirsearch web discovery, exposure checks, secret/API-key scanning, Moodle auditing, reflected-XSS and SQLi checks, Hydra credential attacks, and WordPress wp2shell processing. Full intensity actively invokes sqlmap and Hydra; recon mode lists those candidates instead. It uses external repositories installed by `setup` for PHP-CGI, React2Shell, WordPress, and directory-scanning capabilities. Built-in CVE probes target PHPUnit eval-stdin RCE (CVE-2017-9841), Apache traversal/LFI (CVE-2021-41773), Struts S2-045 (CVE-2017-5638), Confluence OGNL RCE (CVE-2022-26134), Drupalgeddon2 (CVE-2018-7600), Next.js middleware bypass (CVE-2025-29927), PHP-CGI (CVE-2024-4577/CVE-2024-8926), and React Server Components RCE (CVE-2025-55182). Several internal checks use benign confirmation markers/arithmetic oracles, but the overall repository is an active exploitation platform: full mode can perform credential guessing and injection, external wp2shell can pursue SQLi-to-shell, and React2Shell can be configured away from safe-check mode to run a command. Notable collection functionality includes downloading exposed files and backups, scanning their contents for cloud/VCS/payment/API credentials, and `gitdump.py`, which mirrors an exposed `.git` directory, retrieves reachable loose Git objects, and reconstructs source files. Artifacts, reports, findings, and potentially sensitive material are stored under `runs/<run-id>/`; report code serializes evidence and can therefore retain sensitive values. ScopeGuard supports target/CIDR and subdomain allowlisting, but supplied documentation/configuration describe scope enforcement as disabled by default, materially increasing operator-supplied target risk.yeee3642 · Disclosed Aug 26, 2026 · python · bash · network · webOperationalCVE-2018-7600The supplied repository contains a standalone Python exploit, drupal.py (7,870 bytes), and a standard Python .gitignore (4,664 bytes). No README, dependency manifest, tests, or framework integration is present. Repository URL, git reference, and archive size were not provided; size_bytes is therefore an unknown-value placeholder of 0, while the supplied file sizes total 12,534 bytes. The script normalizes an operator-supplied target URL, fingerprints Drupal through up to three GET requests, and submits a Drupal 8-style registration AJAX payload for CVE-2018-7600. It attempts to turn attacker-controlled render-array properties into a PHP exec callback. The command is selectable through a positional argument and defaults to id. Requests use 10-second detection timeouts and a 15-second exploit timeout; the exploit POST includes a fixed Firefox 28 user-agent and form-urlencoded content type. Important limitations include inaccurate Drupal 8 version classification: only major and minor numbers are parsed, so vulnerable 8.5.0 can be labeled likely patched, while patched 8.3 and 8.4 releases can be labeled likely vulnerable. Patch warnings do not prevent exploitation. Drupal 7 is mentioned but lacks a matching exploit implementation. Success checks rely on HTTP 200 and broad strings such as root or www-data, allowing false positives; command execution can also occur without recognizable output. The unused verify_shell helper assumes an existing vuln.php endpoint but supplies no shell-installation payload. There are no fixed attacker-controlled callback destinations, exfiltration routines, or evident fake-exploit behavior. Static analysis establishes the exploitation intent, not successful execution against a live target.K52-ai · Disclosed Oct 4, 2026 · python · webOperationalvulhub-drupal-cve-2018-7600This repository is primarily a deliberately vulnerable Drupalgeddon 2 training lab, with a valid manual exploit request embedded in its English and Chinese walkthroughs. The request abuses attacker-controlled Form API render-array keys beginning with # to invoke PHP exec with the hardcoded id command. It demonstrates CVE-2018-7600 without login, but no standalone exploit program, reverse shell, persistence, or exfiltration logic is supplied. Its operational maturity reflects the documented basic command payload, not an automated exploitation tool. All 31 supplied files were reviewed. The 14 code files comprise seven Terraform modules, one Ruby Vagrantfile, five shell scripts, and one Dockerfile; YAML supplies additional deployment and CI configuration. isoloom.yml defines one Drupal 8.5.0 machine, and .isoloom/ contains generated Docker, Kubernetes, local-VM, Proxmox, and six cloud-provider deployment variants. app/ vendors the upstream walkthroughs and minimal Compose file; base/ contains a Dockerfile extending drupal:8.5.0 rather than Drupal application source. The root documentation records Vulhub provenance, .ctf/ provides challenge metadata, and GitHub workflows validate and publish the lab. Isoloom is deployment tooling, not an exploit framework. The shell checks verify installer availability, a Drupal 8.5.0 asset-version marker, and blocked outbound HTTP; they do not execute the exploit or conclusively test vulnerability. Docker isolation removes default routing, while Kubernetes uses egress policies whose effectiveness depends on network-policy enforcement. Kubernetes publishes a LoadBalancer on port 8080 without an explicit client allowlist; cloud firewall modules restrict ports 22 and 8080 using allowed_cidr. Docker installation and Debian-image downloads are provisioning traffic, and 1.1.1.1 is an isolation probe rather than command-and-control infrastructure. CI cleanup and provisioning rm -rf commands have legitimate setup purposes and do not indicate a fake exploit. The current repository URL, analyzed Git ref, and archive size were not supplied; empty strings and zero represent unavailable metadata. The recorded Vulhub commit identifies vendored upstream provenance only.CyberCTF · Disclosed Oct 8, 2026 · shell · hcl · webOperationalDrupalgeddon2-pythonThe supplied 100-file snapshot contains one standalone exploit, exploitdrupal.py (2,114 bytes), surrounded by a bundled Python 3.12 virtual-environment tree. The 66 code/script files comprise 57 Python files, five Python console wrappers, and four shell/PowerShell activation scripts. Most files are dependency code or package metadata for certifi, charset-normalizer, idna, and pip, rather than additional exploits. Some dependency contents are truncated, so their complete behavior cannot be audited from this material. The main function, explotar_drupalgeddon2, implements the Drupal 8 registration-form technique for CVE-2018-7600 (Drupalgeddon2). It adds http:// when the target has no scheme, removes trailing slashes, and sends a form-encoded POST to /user/register with the characteristic element_parents, ajax_form, and _wrapper_format parameters. Attacker-controlled mail render properties select passthru as a post-render callback and supply the requested OS command as markup. Although the CVE also affects other Drupal branches, this script contains only the Drupal 8-style request, not a Drupal 7 exploitation flow. The affected version ranges listed here are vulnerability context; the script itself neither detects nor validates versions. The request has a 10-second timeout, disables TLS certificate verification, and suppresses insecure-request warnings. For HTTP 200 responses, it prints text preceding the literal AJAX marker '[{"command"', or the entire response if that marker is absent. HTTP 200 and nonempty response text do not prove command execution; the script can misleadingly report execution when no output is present. There is no preliminary vulnerability check, authentication flow, interactive session, alternate callback, or exploitation fallback. The command is configurable through sys.argv[2], but the exploit route and callback are fixed. This is a basic operational command-execution exploit, not merely a detector, with no apparent fake-exploit behavior in the main file. Its help text names drupalgeddon2.py even though the supplied file is exploitdrupal.py. Requests and standalone urllib3 are imported but are not included in the listed snapshot, so dependency completeness is unconfirmed. Absolute virtual-environment paths further reduce portability. No fixed victim IP, callback server, or exfiltration destination is embedded; dependency documentation links are not exploit network calls. Repository URL, git reference, and archive size were not supplied; empty strings and zero represent unavailable metadata.Alexnpc18 · Disclosed Oct 22, 2026 · python · powershell · webOperationalCVE-2018-7600This repository provides a proof-of-concept exploit for CVE-2018-7600 (Drupalgeddon 2), targeting vulnerable versions of Drupal (before 7.58, 8.x before 8.3.9, 8.4.x before 8.4.6, and 8.5.x before 8.5.1). The main exploit is implemented in 'exploit.py', a Python script that sends a crafted POST request to the Drupal user registration endpoint, exploiting the form API to execute arbitrary shell commands. The payload writes a file ('hello.txt') to the web server to demonstrate successful exploitation. The repository also includes ModSecurity and .htaccess rules (in 'ModSecurity.txt' and 'htaccess.txt') to help protect against this attack vector. The README provides context, references, and mitigation advice. The exploit is a network-based remote code execution PoC and does not include weaponized or post-exploitation features.a2u · Disclosed Mar 30, 2018 · python · networkPoCCVE-2018-7600This repository is a proof-of-concept (PoC) exploit for CVE-2018-7600, also known as Drupalgeddon 2, which is a critical remote code execution vulnerability in Drupal Core. The main entry point is 'exploit.php', which prompts the user for a target URL and invokes the exploit logic in 'src/CVE-2018-7600.class.php'. The exploit works by sending a specially crafted POST request to the '/user/register' endpoint of a Drupal site, abusing form rendering to execute arbitrary commands. The payload downloads a file ('hello.txt') from a remote GitHub URL and writes it to the web root of the target server, demonstrating successful code execution. The exploit checks for the presence of this file to confirm vulnerability. The code is written in PHP and uses external libraries for HTTP requests and random user agents. The repository is structured with a clear separation between the exploit logic and the entry point, and includes a README with usage instructions and references. No fake or destructive behavior is present; the exploit is a legitimate PoC for educational and testing purposes.dwisiswant0 · Disclosed Apr 14, 2018 · php · networkPoCCVE-2018-7600This repository is a proof-of-concept exploit for CVE-2018-7600 (Drupalgeddon 2), targeting vulnerable Drupal installations (versions before 7.58, 8.x before 8.3.9, 8.4.x before 8.4.6, and 8.5.x before 8.5.1). The main exploit logic is implemented in 'exploiter.py', a Python script that automates the exploitation process. The script reads a list of target URLs from a file (e.g., 'hosts.txt'), checks if the site is up and running Drupal, and then sends a specially crafted POST request to the Drupal AJAX user registration endpoint. The payload leverages the 'exec' post-render callback to execute arbitrary shell commands on the server. By default, it writes the output of the 'id' command to a randomly named file on the target, which is then checked for existence to confirm exploitation. The script supports optional Tor proxying for anonymity and can clean up after itself by deleting the created file. The repository includes supporting files such as a README with usage instructions, a requirements.txt for dependencies, and notes/todo files. No hardcoded credentials or real-world endpoints are present; 'https://example.com' is used as a placeholder.thehappydinoa · Disclosed Apr 15, 2018 · python · networkPoCCVE-2018-7600This repository contains a proof-of-concept exploit for CVE-2018-7600, a critical remote code execution vulnerability in Drupal 7.x versions prior to 7.58. The exploit is implemented in a single Python script (poc.py) that uses the requests library to interact with a vulnerable Drupal instance. The script crafts specific POST requests to Drupal's user/password and file/ajax endpoints, abusing the form API's #post_render and #markup properties to execute arbitrary system commands (demonstrated with 'id'). The target server's URL must be set in the HOST variable. The exploit demonstrates successful code execution by printing the output of the 'id' command, confirming the vulnerability. The repository is simple, containing only a README and the exploit script, and is intended for demonstration and testing purposes.firefart · Disclosed Apr 16, 2018 · python · networkPoC
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Debian ProjectDebian Linuxoperating_system
DrupalDrupalapplication
FAQ

Frequently asked questions

Is CVE-2018-7600 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Nov 3, 2021.
Is there a public exploit for CVE-2018-7600?
Yes. Mallory tracks 30 public exploits or proofs of concept for CVE-2018-7600, the earliest disclosed Mar 28, 2018.
Is there a patch for CVE-2018-7600?
Upgrade Drupal core to a supported, patched release. Historical fixes for this vulnerability are Drupal 7.58, 8.3.9, 8.4.6, and 8.5.1 for their respective branches.
What products are affected by CVE-2018-7600?
Drupal and Debian Project Debian Linux.
How severe is CVE-2018-7600?
CVE-2018-7600 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 100.0% (100th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

31 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+17 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence3Every report linking this CVE to a named adversary.
Associated malware21Malware families linked to this CVE, with evidence and IOCs.
Detection signatures5YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.