Other news

pretalx patches a high-severity cross-site scripting flaw in organiser search

Version 2026.1.0 of the open-source call-for-papers tool fixes CVE-2026-41241, a stored XSS bug rated 8.7 that could hijack organiser sessions.

April 17, 2026 · Confirmed with 4 sources

Cover image: pretalx patches a high-severity cross-site scripting flaw in organiser search

pretalx, the open-source call-for-papers and conference scheduling tool, has fixed a stored cross-site scripting vulnerability in its organiser search, tracked as CVE-2026-41241. The project's security advisory, published on GitHub on April 17, 2026, rates it high severity with a CVSS 3.1 score of 8.7. All versions before 2026.1.0 are affected, and 2026.1.0 is the patched release.

According to the advisory, the organiser search dropdown displayed submission titles, speaker display names and user names or emails without escaping them. Someone who controls one of those fields, such as a speaker submitting a talk, could plant a script that runs in an organiser's browser when the organiser's search matches that record. The advisory says the script could read the CSRF token, send authenticated requests and pull visible data. It only triggers for organisers with more than review permissions, or administrators.

Security firm Rescana wrote up the flaw on May 28, warning that it could be abused to hijack sessions or accept talks automatically. Rescana's headline calls it critical, but both its own page and the advisory give the 8.7 score, which falls in the high band. The advisory credits Elad Meged of Novee Security with the report.

Our data lists pretalx as open-source conference content software that can be self-hosted or used as a hosted service.

Why it matters for event marketers: Event teams that self-host pretalx for a speaker call should confirm they're on 2026.1.0 or later, since speaker-submitted fields were the attack path.

Why call-for-papers tools are a target

A call for papers is one of the few places where an event invites anyone on the internet to type into its systems. Speakers create accounts, write titles and abstracts and set their own display names, and organisers with wide permissions then read all of it. That's the pattern CVE-2026-41241 exploited: text a submitter controls, shown unescaped to a privileged user, can act with that user's rights, which in a CFP tool can mean accepting talks or pulling speaker data.

The same release closed a separate flaw, CVE-2026-41426, published as GitHub advisory GHSA-jm8c-9f3j-4378 on April 17 and rated moderate with a CVSS 3.1 score of 6.1. User-controlled placeholders in pretalx's email templates, such as an account display name, weren't escaped, so an unauthenticated attacker could get an instance to send HTML-rendered email from the event's own sender address.

The advisory says the easiest route was the password reset flow: register an account with a crafted name, enter a victim's email address and trigger a reset. Because the message comes from the legitimate sender, it passes SPF, DKIM and DMARC checks, which makes it useful for phishing. Acceptance and rejection emails had the same problem. Mark Fijneman is credited with the report, which the maintainers say covered part of the issue and led them to the wider bug.

What pretalx 2026.1.0 changes beyond the fixes

pretalx released version 2026.1.0 on April 15, 2026, two days before the advisories went public. The release post describes the two fixes as critical security issues and says that, to the team's knowledge, neither had been exploited in the wild. Events on the hosted pretalx.com service were already running the fixed version, so hosted customers didn't need to do anything.

The release also rebuilt the call-for-papers editor with a live preview and drag-to-reorder fields, added speaker profiles that carry across events, introduced blocker sessions that reserve schedule slots without publishing them, and added schedule filters for session language and non-recorded sessions.

How to keep self-hosted conference software patched

The XSS advisory says there's no configuration workaround. Operators who can't upgrade right away can avoid the organiser search bar, or manually patch the organiser JavaScript file named in the advisory and re-collect static files. Its CVSS vector shows a network attack with low complexity that needs a low-privileged account and an organiser's interaction, with a changed scope.

Rescana said that, as of its May 28 write-up, no public proof-of-concept exploit or indicators of compromise had been published. It suggested that teams delaying the upgrade review recent submissions for suspicious content in titles, display names and email fields, and watch organiser accounts for unusual activity such as mass talk acceptances.

Self-hosting moves patching onto the event team. Watch the project's GitHub security advisories, upgrade before the CFP opens and again before review starts, and give review-only access to anyone who doesn't need more, since the XSS only fired for organisers above review permissions. Hosted services patch for you, but it's still worth checking how fast. Our guide to security reviews for event software covers the questions to put to any vendor or open-source project.

Frequently asked questions

Which pretalx version fixes CVE-2026-41241?
Version 2026.1.0 fixes CVE-2026-41241, and all earlier versions are affected. The same release also fixes CVE-2026-41426, a moderate email injection flaw in pretalx's mail templates. Self-hosted operators should upgrade to 2026.1.0 or later; the advisory lists no configuration workaround for the XSS bug.
Do pretalx.com hosted users need to update?
No. The pretalx team says events on the hosted pretalx.com service were already running the fixed release when 2026.1.0 was announced, so hosted organisers didn't need to do anything. The upgrade advice applies only to instances that event teams run on their own servers.
What is a stored cross-site scripting vulnerability?
It's a flaw where an application saves text a user typed and later shows it to other users without escaping it, so a hidden script in that text runs in their browsers. In pretalx's case, a speaker could plant a script in a submission title or display name that ran when an organiser searched, with the organiser's permissions.
Is it safe to self-host call for papers software?
It can be, if someone owns patching. Self-hosted tools such as pretalx give you control of speaker data and no licence fee, but you have to follow security advisories, upgrade promptly and limit organiser permissions. If nobody on the team will do that, a hosted service that applies fixes for you is usually the safer choice.
How can event teams check if their CFP was attacked?
Rescana suggests reviewing recent submissions for odd content in titles, display names and email fields, and checking organiser accounts for unusual activity such as mass talk acceptances. For the email flaw, look for password reset requests on accounts you don't recognise. Neither the advisories nor Rescana reported public exploits or indicators of compromise.

Sources

We confirm every story with at least two sources before publishing. Checked 2026-10-19.

  1. Stored cross-site scripting in organiser search typeahead · pretalx (GitHub Security Advisory) · Company announcement
  2. CVE-2026-41241: Critical Stored XSS in Pretalx Conference Platform Allows Attackers 100% Talk Acceptance (Patched in 2026.1.0) · Rescana · Press coverage
  3. Email injection via unescaped user-controlled placeholders in pretalx mail templates · pretalx (GitHub Security Advisory) · Company announcement
  4. Releasing pretalx v2026.1.0 · pretalx · Company announcement