Loading vulnerability…
CVE-2023-28458 affects pretalx 2.3.1 before 2.3.2. The vulnerability exists in the HTML export functionality, which is described as a non-default feature. Due to a path traversal flaw, an organizer can cause the application to write outside the intended export path and overwrite an arbitrary file. The overwritten content is the standard pretalx 404 page content, indicating the issue is an arbitrary file overwrite via directory traversal rather than direct attacker-controlled file content injection.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit auxiliary module targeting CVE-2023-28459, a vulnerability in Pretalx (<=2.3.1) that allows arbitrary file read and limited file write via the schedule export feature. The exploit works by registering a malicious proposal that references a file to be read (e.g., /etc/passwd) using an HTML tag. After logging in with valid credentials, the module automates the process of submitting, approving, and scheduling the proposal, then triggers the export of the schedule as a zip file. The targeted file is included in the zip and extracted by the module, with the contents stored as loot. The module requires user credentials with sufficient permissions and the conference name and media URL. The code is written in Ruby and is designed to be used within the Metasploit framework. The main attack vector is network-based, exploiting the Pretalx web application's schedule export functionality.
This repository contains a single Metasploit module targeting CVE-2023-28458, a limited file write vulnerability in Pretalx (up to version 2.3.1) when running in debug mode. The exploit leverages authenticated access to the Pretalx backend to register a proposal, upload a malicious Python .pth file as a resource, and then abuses a path traversal to write this file into the Pretalx user's site-packages directory. This results in remote code execution as the Pretalx user whenever Python code is run by Pretalx. The module requires valid Pretalx backend credentials and knowledge of the Python version on the target. The exploit is operational, providing a customizable command execution payload. The main file is written in Ruby and follows the standard Metasploit module structure, with clear separation of initialization, checking, and exploitation logic. No hardcoded IPs or domains are present, but file system paths relevant to the exploit are fingerprintable.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.