dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-49376

MEDIUM · 5.3 CVSS v3.1 Published 2025-10-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/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 DELUCKS DELUCKS SEO delucks-seo allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects DELUCKS SEO: from n/a through <= 2.5.9.

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

The delucks-seo WordPress plugin versions up to 2.5.9 contain a missing authorization vulnerability that allows users to access functionality not properly constrained by access control lists. This authorization bypass could permit unauthenticated or low-privilege users to perform actions that should require higher privileges.

MitigationUpdate to the latest version of delucks-seo plugin when available, or implement web application firewall rules to restrict access to the vulnerable endpoints until a patch is released.

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

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. Locate the delucks-seo plugin installation
    Check if the delucks-seo plugin directory exists in your WordPress installation under wp-content/plugins/delucks-seo/
    Affected if The plugin directory exists and the plugin is installed
  2. Identify the installed version
    Open the main plugin file (usually delucks-seo.php) in the plugin directory and locate the Version header comment, or check the version displayed in the WordPress admin under Plugins > Installed Plugins
    Affected if The version number returned is 2.5.9 or lower
  3. Verify the plugin is active
    Check the WordPress admin under Plugins > Installed Plugins to confirm whether delucks-seo is activated
    Affected if The plugin shows as Active and the version is 2.5.9 or lower
  4. Confirm authorization bypass exposure
    Review access to plugin endpoints or admin functions - the vulnerability allows users to access functionality not properly constrained by ACLs, meaning lower-privilege users can reach admin-level actions
    Affected if The plugin is active at a vulnerable version and exposes functionality that should require higher privileges

You are affected if the delucks-seo plugin is installed, active, and running version 2.5.9 or lower, as this version range contains the missing authorization vulnerability.

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 to the latest version of delucks-seo plugin when available, or implement web application firewall rules to restrict access to the vulnerable endpoints until a patch is released.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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