Skip to main content
Menu
CVEs

Simple Membership WP User Import cross-site request forgery in add_selective action

CVE-2026-127201Published , updated

4.3MediumCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Summary

The Simple Membership WP user Import plugin for WordPress has a cross-site request forgery flaw in its add_selective action, caused by missing or incorrect nonce validation. A remote attacker with no login can trick a site administrator into clicking a malicious link, which lets them import arbitrary WordPress users into Simple Membership and change their roles through the membership-level-to-role mapping.

Written by a model

Original description

The Simple Membership WP user Import plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.9.2 This is due to missing or incorrect nonce validation on the add function. This makes it possible for unauthenticated attackers to import arbitrary WordPress users into Simple Membership and modify their WordPress role via the plugin's membership-level-to-role mapping via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. Successful exploitation additionally requires an action by an administrator — the attacker cannot trigger the vulnerability on their own.

What to do

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-127201 (Simple Membership WP user Import <= 1.9.2 - Cross-Site Request Forgery to add_selective Action), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-127201 (entry last updated 2026-11-20):
Affected:
- wpinsider-1 Simple Membership WP user Import: through 1.9.2
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-127201 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-127201 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/ce9f2d32-7335-42ea-9aeb-7a688e0e7266?source=cve
- https://plugins.trac.wordpress.org/browser/simple-membership-wp-user-import/tags/1.9.2/classes/class.swpm-wp-import.php#L37
- https://plugins.trac.wordpress.org/browser/simple-membership-wp-user-import/tags/1.9.2/views/wp_user_list.php#L62
- https://plugins.trac.wordpress.org/browser/simple-membership-wp-user-import/tags/1.9.2/classes/class.swpm-wp-import.php#L38
- https://downloads.wordpress.org/plugin/simple-membership-wp-user-import.1.9.3.zip
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-127201
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-127201"}.

Affected versions

cve.now Index

16Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity4.3/10CVSS 4.3
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 71 if added to CISA KEV
  • Would score about 66 if CISA's SSVC rates exploitation active
  • Would score about 31 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 7

Questions about CVE-2026-127201

Is CVE-2026-127201 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-127201?

Simple Membership WP user Import: through 1.9.2.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.