CVE-2026-16146
Received Received - Intake

SQL Injection in Invisible Anti-Spam & CAPTCHA WordPress Plugin

Vulnerability report for CVE-2026-16146, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-15

Last updated on: 2026-08-15

Assigner: Wordfence

Description

The Invisible Anti-Spam & CAPTCHA β€” reCAPTCHA Alternative for All Forms plugin for WordPress is vulnerable to generic SQL Injection via Pattern JSON Keys/Values in all versions up to, and including, 5.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with editor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-15
Last Modified
2026-08-15
Generated
2026-08-15
AI Q&A
2026-08-15
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
invisible_anti_spam recaptcha_alternative_for_all_forms to 5.1 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
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 Quick Actions

Instant insights powered by AI
Executive Summary

This WordPress plugin has a SQL injection flaw due to improper escaping of user input in JSON keys/values. Attackers with editor-level access or higher can inject malicious SQL queries to extract sensitive data from the database.

Detection Guidance

This vulnerability requires authenticated access with editor-level permissions or higher. Detection involves checking for unusual database queries or patterns in logs. Review WordPress plugin logs for suspicious JSON key/value patterns in requests to the plugin. No specific commands are provided in the context.

Impact Analysis

If you use this plugin, attackers could steal sensitive information from your WordPress database, such as user credentials or personal data. The impact is limited to authenticated users with editor access or higher.

Compliance Impact

This vulnerability could lead to unauthorized data access, potentially violating GDPR (data protection) or HIPAA (health data privacy) if sensitive user information is exposed. Compliance may be compromised if data breaches occur.

Mitigation Strategies

Immediately update the plugin to the latest version if an update is available. If not, consider disabling the plugin temporarily until a patch is released. Restrict editor-level and higher user roles to minimize exposure. Monitor database activity for unauthorized queries.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-16146. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart