# CVE-2026-105983: Email Marketing 4Dem <= 2.0.5 - Unauthenticated Settings Modification and Configuration Disclosure

Status: published. Published: 2026-11-14. Updated: 2026-11-14.

The Email Marketing 4Dem WordPress plugin through 2.0.5 does not perform authorization or capability checks on several of its AJAX actions and REST routes, allowing unauthenticated users to disclose the Email Marketing 4Dem WordPress plugin through 2.0.5's stored configuration and data and to modify its stored settings.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Unknown / Email Marketing 4Dem: ≥ 0; ≤ 2.0.5 (affected, semver). Source: CNA: WPScan

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-862

## Exploit evidence

- exploit: https://wpscan.com/vulnerability/9f280371-d1de-4bf9-8200-44b8e3e4b71d/ (CNA: WPScan)

## References

- https://wpscan.com/vulnerability/9f280371-d1de-4bf9-8200-44b8e3e4b71d/ (CNA: WPScan; exploit, vdb-entry, technical-description)

## Provenance

- CNA: WPScan: https://www.cve.org/CVERecord?id=CVE-2026-105983; retrieved 2026-11-14; source updated 2026-11-14

Revision: 448bb929127fd2131c4620ff6c5cf84f0ab7d19810e3c0c236056c74748c57e2

Canonical: https://y2.dev/cve/CVE-2026-105983

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.