CVE-2025-13619
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 Flex Store Users plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.1.0. This is due to the 'fsUserHandle::signup' and the 'fsSellerRole::add_role_seller' functions not restricting what user roles a user can register with. This makes it possible for unauthenticated attackers to supply the 'administrator' role during registration and gain administrator access to the site. Note: The vulnerability can be exploited with the 'fs_type' parameter if the Flex Store Seller plugin is also activated.
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 Flex Store Users plugin for WordPress fails to validate or restrict user role assignment during registration via the fsUserHandle::signup and fsSellerRole::add_role_seller functions. Unauthenticated attackers can supply the 'administrator' role via the 'fs_type' parameter when the Flex Store Seller plugin is active, gaining full administrative access to the WordPress site.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Verify Flex Store Users plugin is installedGo to WordPress admin dashboard > Plugins > Installed Plugins, look for 'Flex Store Users' in the listAffected if the plugin is installed and active
-
Check Flex Store Users plugin versionIn Plugins list, click on the plugin to view details, or check the plugin header in /wp-content/plugins/flex-store-users/ directory for version numberAffected if the installed version is 1.1.0 or below (the vulnerability is present in unpatched versions up to 1.1.0)
-
Verify Flex Store Seller plugin statusCheck Plugins list for 'Flex Store Seller' plugin - this plugin must be active for the vulnerability to be exploitableAffected if Flex Store Seller plugin is installed and active alongside Flex Store Users
-
Confirm user registration is enabledIn WordPress admin, go to Settings > General > Membership, verify 'Anyone can register' is checkedAffected if user registration is enabled on the site (the attack vector requires this setting)
-
Audit administrator accounts for unauthorized usersGo to Users > All Users in WordPress admin, review the list of users with Administrator role for unknown or suspicious accountsAffected if there are administrator accounts you did not create or recognize
You are affected if Flex Store Users plugin (version 1.1.0 or below) is active alongside Flex Store Seller, user registration is enabled, and an unauthorized administrator account exists on the site.
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 the Flex Store Users plugin to a patched version above 1.1.0 as soon as available; alternatively, disable the plugin entirely or restrict registration endpoints at the web server level until a patch is applied.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13619 — 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-13619 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