CVE-2026-32433
Blind SQL Injection in CP Contact Form with Paypal
Publication date: 2026-03-13
Last updated on: 2026-03-13
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| codepeople | cp_contact_form_with_paypal | to 1.3.61 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': 'CVE-2026-32433 is a SQL Injection vulnerability found in the WordPress plugin "CP Contact Form with Paypal" versions up to and including 1.3.61.'}, {'type': 'paragraph', 'content': "This vulnerability allows a malicious actor with contributor or developer privileges to inject special SQL commands into the plugin's database queries, potentially enabling unauthorized interaction with the database."}, {'type': 'paragraph', 'content': 'Specifically, it is a Blind SQL Injection, meaning the attacker can infer information from the database without directly seeing the data returned.'}] [1]
How can this vulnerability impact me? :
[{'type': 'paragraph', 'content': "This vulnerability can allow an attacker to manipulate or steal data from the plugin's database."}, {'type': 'paragraph', 'content': 'Although the CVSS score is high (8.5), indicating a serious security risk, the actual impact is considered low in typical WordPress environments due to the requirement of contributor or developer privileges to exploit it.'}, {'type': 'paragraph', 'content': 'Potential impacts include unauthorized data access, data manipulation, and possible disruption of service.'}, {'type': 'paragraph', 'content': 'Users are strongly advised to update to version 1.3.62 where the vulnerability has been patched.'}] [1]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': "This vulnerability is a Blind SQL Injection in the CP Contact Form with Paypal WordPress plugin up to version 1.3.61. Detection typically involves monitoring for unusual database queries or attempts to exploit SQL injection vectors in the plugin's input fields."}, {'type': 'paragraph', 'content': 'Since the vulnerability requires contributor or developer privileges to exploit, detection can focus on reviewing logs for suspicious activity related to these roles.'}, {'type': 'paragraph', 'content': 'Specific commands are not provided in the available resources, but general approaches include using web application scanners that test for SQL injection or manually testing input fields of the plugin for injection payloads.'}] [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate step to mitigate this vulnerability is to update the CP Contact Form with Paypal plugin to version 1.3.62 or later, where the issue has been patched.
Additionally, enabling auto-updates for the plugin can help ensure that future vulnerabilities are addressed promptly.
Limiting contributor or developer privileges to trusted users can also reduce the risk of exploitation.