☠️
EXFILTRATING
DATA...
01010111 10110010 00101001 11000110 01101100 10011011 00010001 11100101 01000010 10101111
[ <-- BACK_TO_SEARCH ]
Tielabs logo [ WEBSITE ] [ VENDOR STATS ]
CVSS: 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N 🐛 CWE-79
👁️
Common Weakness Enumeration - Identifies the specific category of software weakness or flaw.

CVE-2025-64208

CVE-2025-64208 Cross-Site Scripting in Tielabs
📅 PUBLISHED: 2025-10-29 08:38 UTC 🔄 UPDATED: 2026-10-08 23:10 UTC
[ PATCH UNDER REVIEW ↓ ] Remains UNDER REVIEW until an independent source confirms the fix
[ DEFENSE PATCH ↓ ]
💣 PoC: Public
👁️
Proof of Concept - Indicates if functional exploit code is publicly available, drastically increasing the risk of immediate attacks.
🎯 EPSS: 0.03%
👁️
0.03% probability
<1× above the median CVE
Tier: LOW
30-day exploitation window · FIRST.org · updated daily
🥷 MITRE: T1059.007
👁️
MITRE ATT&CK Tactic - Describes the strategy hackers use to execute this attack.
Country: Estonia License: Freemium
VULNERABLE: version not auto-detected — verify your deployed version locally
CVSS VECTOR BREAKDOWN 6.5
AV: N Attack Vector Network
AC: L Attack Complexity Low
PR: N Privileges Required None
UI: R User Interaction Required
S: C Scope Changed
C: L Confidentiality Low
I: L Integrity Low
A: N Availability None
6.5
THREAT LEVEL
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

CVE-2025-64208 is a DOM-Based Cross-Site Scripting (XSS) vulnerability in the TieLabs Jannah - Extensions WordPress plugin, affecting versions through 1.1.4. The vulnerability arises from improper neutralization of user-controlled input during web page generation, allowing an attacker to inject malicious scripts that execute in the victim's browser within the context of the WordPress site. Since this is a WordPress plugin, the attack surface is limited to sites running the Jannah theme with the vulnerable extensions module enabled. No public exploit code or proof-of-concept has been released, and the EPSS score is 0.0%, indicating low exploitation activity. However, the lack of a patch from the vendor increases risk for unmaintained installations.

⚡ AUTOMATE YOUR CVE INTELLIGENCE

This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.

›Patch confidence — UNVERIFIED to CONFIRMED, cross-referenced NVD + RHSA + Debian
›Exploit & PoC — poc_status, poc_url, has_exploit. Not in NVD.
›Shodan dorks — ready-made queries to find exposed vulnerable systems
›Detection rules — YARA · Wazuh · Elastic (all plans) · Sigma (Pro)
›pending_fields — know exactly which of 7 fields NVD hasn't processed yet
›Free backfill — data incomplete when you paid? Re-check within 30 days = 0 credits
PAYG €0.08/lookup Standard €19/mo (was €29) · 5k credits Pro €65/mo (was €99) · 20k credits FOUNDING PRICE · LOCKED FOR LIFE · ENDS 31 DEC 2026
[ FROM €19/MO ]
Free sandbox key available
No signup required

Supply Chain & Package Security

This vulnerability affects a WordPress plugin distributed via the official WordPress plugin repository and commercial channels. Users who obtained the plugin through legitimate means are at risk if they have not applied any available updates. The absence of a patch from TieLabs means that supply chain integrity is compromised for all versions <= 1.1.4. Administrators should consider removing or replacing the plugin until a fix is released.

CVSS Breakdown & Threat Level

  • Attack Vector (AV): Network (N) – The vulnerability can be exploited remotely.
  • Attack Complexity (AC): Low (L) – No special conditions required.
  • Privileges Required (PR): None (N) – No authentication needed.
  • User Interaction (UI): Required (R) – Victim must click a crafted link or visit a malicious page.
  • Scope (S): Changed (C) – The injected script can affect resources beyond the vulnerable component.
  • Confidentiality (C): Low (L) – Limited data exposure possible.
  • Integrity (I): Low (L) – Script can modify content within the victim's session.
  • Availability (A): None (N) – No direct impact on availability.

CVSS Score: 6.5 (Medium)
Threat Level: Medium – Exploitation requires user interaction, but no authentication is needed, and the impact is limited to the client side.

Deep Dive & Mechanics

The vulnerability resides in the jannah-extensions plugin, which extends the functionality of the Jannah WordPress theme. The plugin improperly handles user-supplied input when generating dynamic content in the browser (DOM-based). Specifically, the plugin reads data from document.location, document.URL, or document.referrer and writes it directly into the DOM without proper sanitization or encoding. This allows an attacker to craft a URL containing malicious JavaScript that, when visited by an authenticated administrator or any user, executes in the context of the WordPress admin dashboard or frontend.

The attack flow:

  1. Attacker crafts a URL with a malicious payload in a query parameter or fragment identifier.
  2. Victim clicks the link (e.g., via phishing email or social engineering).
  3. The vulnerable plugin reads the attacker-controlled value from the DOM.
  4. The value is inserted into the page without sanitization, causing the browser to execute the injected script.
  5. The script can steal session cookies, perform actions on behalf of the victim, or deface the site.

Vulnerable vs. Patched Code

Since no patch is available, the vulnerable code pattern is described generically. The plugin likely uses JavaScript code similar to:

// Vulnerable code
var userInput = window.location.hash.substring(1);
document.getElementById('output').innerHTML = userInput;

A patched version would sanitize the input before DOM insertion:

// Patched code
var userInput = window.location.hash.substring(1);
var safeOutput = document.createTextNode(userInput);
document.getElementById('output').appendChild(safeOutput);

Or use a DOMPurify library:

var userInput = window.location.hash.substring(1);
document.getElementById('output').innerHTML = DOMPurify.sanitize(userInput);

Exploitation & Lab Setup

Red Team

Since no public exploit code is available, a proof-of-concept can be constructed. The following HTML/JavaScript demonstrates the vulnerability:

<!-- exploit.html -->
<!DOCTYPE html>
<html>
<body>
<script>
// Simulate the vulnerable plugin behavior
var payload = "<img src=x onerror=alert('XSS')>";
document.write(payload);
</script>
</body>
</html>

To exploit the actual plugin, craft a URL like:

https://victim-site.com/?page_id=123#<img src=x onerror=alert(document.cookie)>

If the plugin reads the fragment identifier and writes it to the DOM, the script executes.

Blue Team

To test for the vulnerability in a lab environment:

  1. Set up a WordPress instance with the Jannah theme and jannah-extensions plugin version 1.1.4.
  2. Create a page or post that uses the vulnerable extension.
  3. Access the page with a crafted URL containing a test payload (e.g., #<script>alert('test')</script>).
  4. Observe if the script executes.

Use browser developer tools to inspect the DOM and verify unsanitized input.

Indicators of Compromise (IOCs)

  • Network: HTTP requests containing suspicious fragment identifiers or query parameters with script tags (e.g., #<script>, ?x=<img src=x onerror=...>).
  • Host: Unexpected JavaScript execution in the browser console, especially in the context of the WordPress admin area.
  • Logs: Web server logs showing requests with unusual fragment identifiers (fragments are not sent to the server, so server-side logging may not capture them; client-side monitoring is required).
  • File: Modified or injected JavaScript files in the wp-content/plugins/jannah-extensions/ directory (if attacker gains write access).

Detection Engineering

YARA Rule

rule CVE_2025_64208_DOM_XSS {
    meta:
        description = "Detects potential DOM-based XSS in Jannah Extensions plugin"
        author = "Valters IT"
        date = "2025-04-10"
        reference = "CVE-2025-64208"
    strings:
        $s1 = "window.location" nocase
        $s2 = "document.location" nocase
        $s3 = "innerHTML" nocase
        $s4 = "jannah-extensions" nocase
    condition:
        all of ($s1,$s2,$s3) or ($s4 and any of ($s1,$s2,$s3))
}

Sigma Rule

title: CVE-2025-64208 DOM-Based XSS in Jannah Extensions
id: 8a3f7c2e-1b4d-4f5a-9c8e-0d1e2f3a4b5c
status: experimental
description: Detects potential exploitation attempts of DOM-based XSS in Jannah Extensions plugin
author: Valters IT
date: 2025-04-10
logsource:
    category: webserver
    product: apache
detection:
    selection:
        c-uri|contains:
            - '#<script'
            - '#<img'
            - '#<svg'
            - '#<iframe'
    condition: selection
falsepositives:
    - Legitimate use of fragment identifiers with HTML-like content (rare)
level: medium

Suricata Rule

alert http any any -> any any (msg:"CVE-2025-64208 DOM-Based XSS Attempt"; flow:to_server; content:"#<script"; http_uri; classtype:web-application-attack; sid:1000001; rev:1;)

Remediation & Mitigation

  1. Immediate Action: Disable or remove the jannah-extensions plugin until a patch is released.
  2. Workaround: Implement a Web Application Firewall (WAF) rule to block requests containing suspicious fragment identifiers (e.g., #<script, #<img).
  3. Code Fix: The vendor should sanitize all user-controlled input before DOM insertion using textContent or a library like DOMPurify.
  4. User Education: Train users to avoid clicking suspicious links, especially those with unusual fragment identifiers.
  5. Monitoring: Enable client-side XSS detection in browsers (e.g., XSS Auditor) and monitor for anomalous JavaScript execution.

Valters IT

👁️ SHODAN DORKS (THREAT HUNTING)

What is this? Security researchers use these exact search queries on Shodan.io (a search engine for internet-connected devices) to find vulnerable systems globally. You can copy these dorks to see if your organization's IP space is exposed.

http.title:"Jannah"
http.html:"jannah-extensions"

💣 PoC CODE AVAILABLE

Exploit code for this CVE is tracked in our database. Access poc_code via API Pro.

[ API_PRO ] →
◈ SOURCE Analysis & enrichment: valtersit.com/cve/CVE-2025-64208/ · CVE data: NVD/MITRE (public domain) · © 2026 ValtersIT Hub
>_ SYSTEM_CORE: INTEL_ACTIVE
90% TEAM-CURATED // 10% AUTOMATED INGESTION.
ALL PATCH REFERENCES AND VERSION DATA SOURCED FROM NVD + OSV OFFICIAL REGISTRIES.