CVE-2025-3609
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Reales WP STPT plugin for WordPress is vulnerable to unauthorized user registration in all versions up to, and including, 2.1.2. This is due to the 'reales_user_signup_form' AJAX action not verifying if user registration is enabled, prior to registering a user. This makes it possible for unauthenticated attackers to create new user accounts, which can be leveraged with CVE-XX to achieve privilege escalation.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Reales WP STPT WordPress plugin fails to verify whether user registration is enabled in WordPress settings before processing the 'reales_user_signup_form' AJAX action. This allows unauthenticated attackers to arbitrarily create new user accounts on the site, which can then be exploited for privilege escalation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm the Reales WP STPT plugin is installedNavigate to WordPress admin > Plugins and look for 'Reales WP STPT' in the list of installed plugins. Note the installed version number.Affected if The plugin is present in the site installation regardless of version.
-
Compare your plugin version to the affected rangeLocate the installed version number from the plugins list and compare it against any official changelog or security advisory for CVE-2025-3609 to see if your version falls within the vulnerable range.Affected if Your installed version has not received the security fix that adds proper user registration validation.
-
Verify if WordPress user registration is enabledGo to WordPress admin > Settings > General and locate the 'Membership' setting 'Anyone can register'. Check whether this box is checked.Affected if The 'Anyone can register' option is enabled, allowing the vulnerable AJAX action to create new user accounts.
-
Check if the signup AJAX endpoint is exposedTest accessing yoursite.com/wp-admin/admin-ajax.php?action=reales_user_signup_form with a tool like curl or browser developer tools. Look for a response that accepts user registration data.Affected if The AJAX endpoint returns a response indicating it accepts the signup form submission without proper validation.
You are affected if the Reales WP STPT plugin is installed and WordPress user registration is enabled, allowing unauthenticated users to create accounts via the vulnerable AJAX action.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate to the latest version of the plugin which includes proper validation of user registration settings. If no update is available, disable user registration in WordPress admin settings or consider removing the plugin until a patch is released.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3609 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-3609 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data