dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-39546

HIGH · 7.6 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
Subscriber Privilege Escalation in MultiLoca <= 4.2.15 versions.

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 confidence

MultiLoca plugin versions 4.2.15 and below contain a privilege escalation vulnerability allowing subscriber-level users to gain elevated administrative privileges. This represents a significant authorization bypass in the WordPress plugin's role handling logic.

MitigationUpdate MultiLoca to the latest patched version immediately. If immediate update is not possible, disable the plugin or restrict subscriber registration until the patch can be applied.

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
High
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check MultiLoca plugin version
    Navigate to WordPress Admin > Plugins > Installed Plugins, locate MultiLoca, and note the version number displayed. Alternatively, access the plugin file via FTP or file manager at /wp-content/plugins/multiloca/ and read the version in the main plugin PHP file header (e.g., multiloca.php).
    Affected if Version is 4.2.15 or lower (including any 4.x.x version below 4.2.15)
  2. Verify WordPress subscriber users exist
    In WordPress Admin, go to Users > All Users and look for any users with the 'Subscriber' role. Alternatively, query the wp_usermeta table for meta_key='wp_capabilities' containing 'subscriber'.
    Affected if At least one user account with Subscriber role exists in the WordPress installation
  3. Confirm subscriber role access is enabled
    Check the MultiLoca plugin settings in WordPress Admin (Plugin Settings or Settings menu) for any options related to user registration, role assignment, or subscriber access. Inspect the plugin configuration database entries if direct database access is available.
    Affected if The plugin has a setting that enables or allows subscriber-level users to interact with privileged administrative functions or role handling

Environment is affected if MultiLoca plugin version is 4.2.15 or lower AND at least one Subscriber role user exists AND the plugin's role handling or subscriber access feature is active.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update MultiLoca to the latest patched version immediately. If immediate update is not possible, disable the plugin or restrict subscriber registration until the patch can be applied.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-39546 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-39546 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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