Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as registered user
-
ExploitInject malicious SQL payload in form field
-
ExecutionExecute blind SQL injection query
-
ImpactExtract sensitive database information
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires valid user login credentials to CP Contact Form with Paypal version <= 1.3.61. SQL injection occurs in contact form input fields processed without parameterized queries. Authentication necessary; no unauthenticated remote exploitation. |
| Impact | The CVSS 3.1 score of 8.5 (High) reflects network-based attack vector with low complexity requiring low privileges and no user interaction. The scope change (S:C) indicates potential impact beyond the vulnerable component, suggesting possible compromise of other applications on shared hosting. However, the absence from CISA's KEV catalog and lack of public exploits suggest this is not currently being actively exploited. Without EPSS data, we cannot assess the statistical likelihood of exploitation. The combination of authentication requirement (PR:L) and blind injection nature makes this less attractive to opportunistic attackers compared to unauthenticated SQL injections, though the scope change elevates concern for shared hosting environments. |
| Exploit ScenarioDerived | An attacker with a low-privileged WordPress account (such as a subscriber or contributor) crafts malicious SQL payloads within form submissions or plugin parameters to extract database contents through blind injection techniques. By observing differences in application response times or error behaviors, the attacker systematically extracts sensitive data like admin credentials or payment information. No public proof-of-concept exists, requiring attackers to develop custom exploitation techniques. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 13, 2026
CP Contact Form with Paypal through version 1.3.61 contains a blind SQL injection vulnerability that allows authenticated attackers to execute arbitrary SQL queries with network access. An attacker with user-level privileges can exploit this flaw to extract sensitive database information, though no patch is currently available.
Earlier versions of this analysis (1)
A SQL injection vulnerability exists in the CP Contact Form with Paypal WordPress plugin that allows authenticated attackers with low privileges to execute blind SQL injection attacks. The vulnerability affects all versions through 1.3.61 and enables attackers to extract sensitive database information including user credentials and potentially compromise other sites on shared hosting environments due to the scope change indicated in the CVSS score. There is no evidence of active exploitation in the wild (not in KEV), no public proof-of-concept code available, and the EPSS score is not provided.
RemediationAI
Update the CP Contact Form with Paypal plugin to a version newer than 1.3.61 if available, though no specific patched version is mentioned in the provided data. As immediate mitigation, restrict access to WordPress admin areas through IP whitelisting or additional authentication layers since the vulnerability requires low-privileged authentication. Implement Web Application Firewall (WAF) rules to detect and block SQL injection attempts, and consider database activity monitoring to detect potential exploitation attempts. Regular security audits of form input handling code should be conducted.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability stems from improper neutralization of special elements used in SQL commands (CWE-89), a classic SQL injection flaw where user input is not properly sanitized before being incorporated into database queries. The CP Contact Form with Paypal plugin (codepeople cp-contact-form-with-paypal) is a WordPress form builder that integrates PayPal payment functionality. The blind SQL injection variant means attackers cannot see query results directly but can infer information through application behavior differences based on true/false conditions in injected SQL statements. No specific CPE identifier is provided in the available data.
Know when Cp Contact Form With Paypal gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
DescriptionCVE.org
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in codepeople CP Contact Form with Paypal cp-contact-form-with-paypal allows Blind SQL Injection.This issue affects CP Contact Form with Paypal: from n/a through <= 1.3.61.
Executive ViewAI
A critical SQL injection vulnerability in CP Contact Form with PayPal (versions ≤1.3.61) could allow attackers to extract sensitive data from your organization's database without triggering typical security alerts. This affects any website using this plugin, potentially exposing customer information, payment records, and business data stored in connected databases.
Disable the CP Contact Form plugin immediately until patch availability is confirmed; implement Web Application Firewall (WAF) rules to detect and block SQL injection patterns; restrict database user permissions to least-privilege access; enable database query logging and monitoring for anomalous activity; consider using a managed security service to monitor the affected endpoints; segment the database from public-facing systems where possible.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
Related Vulnerabilities in SQL Injection Vulnerabilities
View all 5More in Cp Contact Form With Paypal
View allThe "CP Contact Form with PayPal" plugin before 1.2.99 for WordPress has XSS in the publishing wizard via the wp-admin/a
The cp-contact-form-with-paypal (aka CP Contact Form with PayPal) plugin before 1.1.6 for WordPress has CSRF with result
The cp-contact-form-with-paypal (aka CP Contact Form with PayPal) plugin before 1.1.6 for WordPress has SQL injection vi
The "CP Contact Form with PayPal" plugin before 1.2.98 for WordPress has XSS in CSS edition. Rated medium severity (CVSS
EUVD-2026-11969
NVD
CVE.org
EPSS
VulDB
GitHub PoC
Exploit-DB