CVE-2023-41130
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 · uneditedMissing Authorization vulnerability in Premmerce Premmerce User Roles premmerce-user-roles allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Premmerce User Roles: from n/a through <= 1.0.12.
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 confidenceA missing authorization vulnerability in the Premmerce User Roles WordPress plugin (versions up to 1.0.12) allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized users to access or modify user role configurations that should be restricted to higher-privileged administrators.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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.
-
Identify Premmerce User Roles plugin versionIn WordPress admin, go to Plugins > Installed Plugins and locate Premmerce User Roles. The version number is displayed below the plugin name. Alternatively, inspect the main plugin file (typically premmerce-user-roles.php) and look for the 'Version' header in the plugin comment block.Affected if The installed version is 1.0.12 or any earlier version (1.0.x where x is 12 or lower).
-
Verify the plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and confirm that Premmerce User Roles shows as 'Active' under the plugin status.Affected if The plugin is active and the version is 1.0.12 or below.
-
Examine plugin role management capabilitiesLocate the plugin PHP files (usually in wp-content/plugins/premmerce-user-roles/). Search for functions that handle user role creation, modification, or deletion. Check if these functions include capability checks such as 'manage_options' or 'edit_users' before allowing role changes.Affected if Role management functions lack proper capability checks or use weak checks that permit lower-privileged users (e.g., editors, authors) to modify roles.
-
Inspect admin menu registrationCheck the file where add_menu_page or add_submenu_page is called for the plugin. Verify what capability is required to access the role management admin pages.Affected if The admin menu is registered with a capability level lower than 'manage_options' (for example, 'edit_posts' or no capability check), allowing unauthorized access.
-
Audit role modification AJAX or REST endpointsIf the plugin provides AJAX handlers or REST API endpoints for role operations, examine the callback functions. Look for current_user_can() or wp_get_current_user() checks before processing role changes.Affected if AJAX or REST endpoints for role modification lack authorization verification or perform inadequate capability checks.
A user is affected if the Premmerce User Roles plugin is installed at version 1.0.12 or below and role management functionality is accessible to users without full administrator privileges.
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 Premmerce User Roles if a patched release is available, or implement additional access control checks at the application level to verify user permissions before allowing role modifications.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41130 — 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-2023-41130 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