Quick answers
- Is CVE-2024-39311 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2024-39311 being exploited in the wild.
- How severe is CVE-2024-39311?
- Medium severity, with a CVSS score of 4, published 28 March 2025.
- Which products and versions are affected?
- publify_core (RubyGems) < 10.0.2, ECOSYSTEM:introduced=0,fixed=10.0.2.
- Is there a fix for CVE-2024-39311?
- Yes. publify_core (RubyGems): upgrade to 10.0.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2024-39311 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2024-39311?
- Check whether you run publify_core (RubyGems) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- publify_core (RubyGems): upgrade to 10.0.2 or later
bundle update publify_core
Technical details
A stored Cross-Site Scripting (XSS) vulnerability exists in Publify (specifically the publify_core engine) due to improper neutralization of input in the redirect functionality. A user with 'publisher' privileges can create a new redirect with a 'javascript:' URI scheme. While the redirect itself may not execute, the administrative dashboard renders this payload within an 'a' tag's href attribute without sufficient sanitization. If an administrator clicks this link in the overview panel, the malicious JavaScript executes in their session context, potentially allowing for privilege escalation. The vulnerability is patched in version 10.0.2.
Affected products
- publify publify_core < 10.0.2
Identifiers
- CVE-2024-39311
- GHSA-8fm5-gg2f-f66q
Timeline
- 2025-03-28: advisory
- 2025-03-28: disclosed
- 2025-03-28: patched