CVE-2025-32655
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in DevriX Restrict User Registration restrict-user-registration allows Stored XSS.This issue affects Restrict User Registration: from n/a through <= 1.0.1.
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 · moderate confidenceCSRF vulnerability in DevriX Restrict User Registration plugin versions <=1.0.1 allows authenticated administrators to be tricked into submitting malicious requests that inject Stored XSS payloads into the application, which then executes when other users view the affected content.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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.
-
Check if DevriX Restrict User Registration plugin is installedLocate the plugin directory at wp-content/plugins/drx-restrict-user-registration/ or search for files containing 'DevriX Restrict User Registration' in the WordPress plugins folderAffected if The plugin directory exists in the WordPress installation
-
Identify the installed plugin versionOpen the main plugin PHP file (usually drx-restrict-user-registration.php) and check the 'Version' header in the plugin comment block, or check readme.txt for the version fieldAffected if The version number is 1.0.1 or lower
-
Confirm the plugin is activeQuery the WordPress database table wp_options for the option_name containing 'active_plugins', or use the WordPress admin dashboard to verify the plugin statusAffected if The plugin appears in the list of active plugins
-
Verify the plugin handles user registration formsSearch the plugin source code for form handlers related to user registration (look for 'register', 'registration', 'user_register', or form submission handlers in the plugin directory)Affected if The plugin contains code that processes user registration form submissions without apparent nonce verification
You are affected if the DevriX Restrict User Registration plugin is installed, active, and running version 1.0.1 or lower in your WordPress environment.
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 dataUntil an official patch is released, disable or remove the plugin; implement anti-CSRF nonce verification on all state-changing admin actions and ensure proper input sanitization and output encoding.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32655 — 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-32655 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