Security readout for executives and security teams
Plain-English summary
CVE-2026-1075 affects the ZT Captcha WordPress plugin through version 1.0.4. A malicious website or link could cause a logged-in administrator’s browser to change the plugin’s settings without proper authorization checks. The attacker must trick an administrator into taking an action, so this is not a fully remote, no-click issue.
Executive priority
Treat as a medium-priority WordPress hygiene issue. It can alter security-related plugin settings but requires administrator interaction and has no cited active exploitation. Prioritize internet-facing or high-value WordPress sites and resolve during the next maintenance cycle unless exposure is widespread.
Technical view
The issue is a CSRF flaw in save_ztcpt_captcha_settings caused by improper nonce validation. The CVE states the nonce check can be bypassed by sending an empty token value, allowing unauthenticated attackers to modify plugin settings if an administrator is induced to submit a forged request. CVSS is 4.3, CWE-352.
Likely exposure
Exposure is limited to WordPress sites running ZT Captcha versions up to and including 1.0.4, especially where administrators are actively logged in. Sites not using this plugin are not affected. The source bundle does not identify a fixed version.
Exploitation context
No CISA KEV listing is provided, and the supplied sources do not claim active exploitation. Practical exploitation requires administrator interaction, such as clicking a crafted link, while authenticated to WordPress. Impact is limited to plugin settings integrity based on the CVSS vector.
Researcher notes
The affected-range statement says all versions through 1.0.4, but the structured affected metadata in the bundle appears inconsistent. No fixed version is named. Analysis should focus on nonce handling in CaptchaRequest.php around the referenced save settings path and on confirming whether trunk contains a remediation.
Mitigation direction
- Inventory WordPress sites for the ZT Captcha plugin and installed version.
- Check vendor or WordPress plugin guidance for a fixed release or official remediation.
- Update the plugin if a vendor-fixed version is available.
- Disable or remove the plugin if it is not business-critical.
- Remind administrators not to click untrusted links while logged into WordPress.
Validation and detection
- Confirm whether ZT Captcha is installed on each WordPress site.
- Record the installed plugin version and compare it to 1.0.4 or earlier.
- Review plugin settings for unexpected changes.
- Check WordPress administrative logs for suspicious settings-update activity.
- Monitor vendor, Wordfence, and CVE pages for remediation updates.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-1075 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/9f9d6da5-1598-4df4-8efc-306370446443?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/zt-captcha/trunk/request/CaptchaRequest.php#L37CVE reference
- https://plugins.trac.wordpress.org/browser/zt-captcha/tags/1.0.4/request/CaptchaRequest.php#L37CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.