Back to CVE records
Medium 4.3Published Apr 22, 2026

CVE-2026-4121Kcaptcha <= 1.0.1 - Cross-Site Request Forgery to Settings Update

Updated under an hour ago ()

Does this affect you?

It affects ksolves Kcaptcha. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

The Kcaptcha plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to and including 1.0.1. This is due to missing nonce validation in the plugin's settings page handler (admin/setting.php). The settings form does not include a wp_nonce_field() and the form processing code does not call wp_verify_nonce() or check_admin_referer() before saving settings to the database via $wpdb->update(). This makes it possible for unauthenticated attackers to modify the plugin's CAPTCHA settings (enabling or disabling CAPTCHA on login, registration, lost password, and comment forms) via a forged request, granted they can trick a site administrator into performing an action such as clicking a link.

CVSS
4.3 MEDIUM (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Weakness (CWE)
CWE-352
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
Wordfence
NVD analysis
Deferred
Record last updated
Apr 23, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
ksolves Kcaptcha
ksolves:kcaptcha (from the name)
through 1.0.1
CNA record

References

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.