dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-39561

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Missing Authorization vulnerability in Marketing Fire, LLC LoginWP - Pro allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects LoginWP - Pro: from n/a through 4.0.8.5.

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

LoginWP Pro plugin for WordPress contains a missing authorization vulnerability that allows users to access functionality that should be restricted by access control lists. This Broken Access Control (BAC) issue enables privilege escalation or horizontal privilege attacks where users can access functions beyond their intended permissions. The vulnerability exists in versions through 4.0.8.5.

MitigationUpdate LoginWP Pro to the latest version when a patch is released. In the interim, audit user roles and permissions, restrict administrative access to trusted personnel, and consider using a Web Application Firewall to mitigate exploitation attempts.

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
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Confirm LoginWP Pro plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for the loginwp folder, or view installed plugins in WordPress admin under Plugins > Installed Plugins
    Affected if LoginWP Pro plugin is present and active in the WordPress installation
  2. Identify installed LoginWP Pro version
    In WordPress admin, go to Plugins > Installed Plugins and find LoginWP Pro to see the version number, or open the main plugin file (e.g., loginwp.php) and read the 'Version' header in the plugin comments
    Affected if The installed version is 4.0.8.5 or any earlier version (the vulnerability affects versions through 4.0.8.5)
  3. Review user roles with LoginWP access
    Navigate to LoginWP settings (LoginWP > Settings) and examine which user roles are permitted to modify redirect rules,.redirection settings, or user mapping functionality
    Affected if Lower-privileged users (such as Editors, Authors, or Contributors) have access to LoginWP configuration features that should be restricted to Administrators only
  4. Check for unauthorized role modifications
    Go to Users > Users in WordPress admin and verify that no unexpected users have been added with elevated roles, or that existing user roles have not been changed to bypass access controls
    Affected if Users exist with privilege levels they should not have, or unauthorized users have access to admin functionality

A user is affected if LoginWP Pro version 4.0.8.5 or earlier is installed AND the environment allows non-administrator users to access LoginWP settings or administrative functions they should not be able to modify.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update LoginWP Pro to the latest version when a patch is released. In the interim, audit user roles and permissions, restrict administrative access to trusted personnel, and consider using a Web Application Firewall to mitigate exploitation attempts.

Recommended fix Moderate confidence

Latest version of LoginWP Pro (any version > 4.0.8.5)

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate LoginWP (formerly ProfilePress) or LoginWP Pro
  4. 4. Check if an update is available for the plugin
  5. 5. If an update is available, update to the latest version of LoginWP Pro that is newer than 4.0.8.5
  6. 6. After updating, verify that the plugin functions correctly and test the authorization controls

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-39561 — 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-2025-39561 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