CVE-2026-16094
Received Received - Intake

SQL Injection in Invisible Anti-Spam & CAPTCHA WordPress Plugin

Vulnerability report for CVE-2026-16094, 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 the 'key' parameter 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 in versions up to 5.1. The issue is in the 'key' parameter where user input is not properly escaped and SQL queries lack preparation. Authenticated attackers with editor-level access or higher can inject malicious SQL to extract sensitive database information.

Detection Guidance

This vulnerability can be detected by checking for suspicious SQL queries in logs or monitoring for unauthorized database access. Use WordPress debugging tools or plugins to log SQL queries and look for anomalies in the 'key' parameter. No specific commands are provided in the context.

Impact Analysis

If you use this plugin, attackers could steal sensitive data from your WordPress database. This includes user credentials, personal information, or other confidential data stored in the site. The attack requires at least editor-level access.

Compliance Impact

This vulnerability could lead to unauthorized data exposure, violating GDPR and HIPAA requirements for protecting personal and health information. Non-compliance may result in legal penalties and reputational damage.

Mitigation Strategies

Immediately update the plugin to the latest version if available. If not, disable the plugin until a patch is released. Restrict editor-level access to only trusted users and monitor database activity for unusual queries.

Chat Assistant

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

EPSS Chart