
Read-only WordPress User Registration CVE-2026-1492 checker for hidden admins, plugin version, uploads PHP, cron, and compromise IOCs.
Read-only checker for owned WordPress sites that may be affected by CVE-2026-1492 in the User Registration & Membership plugin.
It helps a site owner confirm plugin exposure and look for compromise indicators such as hidden administrator accounts, suspicious uploads, cron entries, and tampered files.
Open a GitHub issue when the checker crashes, gives an unclear result, flags a false positive, or needs documentation cleanup. Keep the example non-sensitive.
Use Ping7 repair when the result is SUSPICIOUS or COMPROMISED, or when the evidence includes live domains, customer data, private logs, admin usernames, upload filenames, or database details that should not be posted in public.
Run from the WordPress root directory, where wp-config.php exists:
curl -fsSLO https://raw.githubusercontent.com/limo57640-crypto/wp-user-registration-vuln-checker/main/check.sh
less check.sh
bash check.sh
Or pass the WordPress path:
bash check.sh /home/example/public_html
CLEAN: no obvious indicators found.SUSPICIOUS: needs manual review.COMPROMISED: strong compromise indicators found.ERROR: script could not complete.WordPress User Registration CVE-2026-1492 Checker
Checks run: 12
Suspicious: 1
Compromised: 0
STATUS: SUSPICIOUS - INVESTIGATE FURTHER
Some checks need manual review.
Guide: https://ping7.cc/cve/wordpress-1492
| Code | Meaning |
|---|---|
0 | Clean result |
1 | Suspicious finding, manual review needed |
2 |
If the result is SUSPICIOUS or COMPROMISED, keep the output and send:
Domain:
WordPress path or host type:
CVE: CVE-2026-1492
Plugin version:
Detector result: CLEAN / SUSPICIOUS / COMPROMISED / ERROR
Symptoms: unknown admin, upload PHP file, redirect, cron, changed theme file, or scanner result
Logs still available: yes / no
Do not send passwords in the first message. Send symptoms, timestamps, screenshots, and sanitized log snippets.
Need repair help: https://ping7.cc/cve-repair
Open an issue for a false positive, a missed defensive signal, or a hosting environment that the checker handles poorly. Include plugin version, WordPress version, host type, and sanitized output. Do not post passwords, API keys, customer data, or live attack strings.
This checker is for owned or client-approved WordPress sites only. It does not exploit the vulnerability and does not modify files.
No payloads. No broad scanning. No exploitation steps.
MIT
| Need | Link |
|---|
| Browse the tool page | https://limo57640-crypto.github.io/wp-user-registration-vuln-checker/ |
| Read the Ping7 self-check guide | https://ping7.cc/cve/wordpress-1492/ |
| Compare with other Ping7 GitHub tools | https://ping7.cc/github-tools/ |
| Send suspicious output for repair | https://ping7.cc/cve-repair/ |
| Area | Signal |
|---|
| WordPress core | Installed core version |
| Plugin exposure | User Registration plugin version and presence |
| Admin accounts | Visible administrators and recent admin creation |
| Hidden admins | wp_usermeta role/capability mismatches |
| Uploads | PHP files under wp-content/uploads/ |
| Config and theme | Obfuscated PHP patterns in critical files |
| Cron | Suspicious scheduled tasks |
| Core folders | Unexpected files in wp-includes |
| Strong compromise indicator found |
3 | Runtime error or WordPress root not found |