dbcve.org
Delucks SeoWordPress extension · Delucks

CVE-2024-30538

CRITICAL · 9.8 CVSS v3.1 Published 2024-06-09
Fix available
A fix is available. Upgrade to 2.5.5 or later.
See remediation →
100/100
Remediation priority · Urgent
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 GmbH DELUCKS SEO.This issue affects DELUCKS SEO: from n/a through 2.5.4.

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

Missing Authorization vulnerability in DELUCKS SEO plugin. This type of flaw allows attackers to bypass access control checks and execute actions without proper authentication or authorization, potentially gaining administrative access to sensitive SEO configuration functions.

MitigationImplement proper role-based access control (RBAC) and authorization checks on all sensitive endpoints and administrative functions within the plugin.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Delucks SeoWordPress extension
Affected:< 2.5.5

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 checks

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

  1. Check the Delucks SEO plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find 'Delucks Seo' in the list. The version number is displayed below the plugin name. Alternatively, check the plugin main file header (usually in wp-content/plugins/delucks-seo/) for the 'Version' tag in the plugin comment block.
    Affected if The installed version is lower than 2.5.5 (e.g., 2.5.4, 2.5.0, 1.x.x, etc.)
  2. Verify the plugin is active
    Confirm the Delucks SEO plugin is enabled and running on the WordPress site. Check the Plugins page status column.
    Affected if The plugin is active and the version is below 2.5.5
  3. Identify if admin endpoints are accessible without authentication
    Test accessing common Delucks plugin admin URLs directly without logging in. Common paths include /wp-admin/admin.php?page=delucks-seo or similar SEO configuration pages. Attempt requests without providing admin credentials.
    Affected if Admin configuration pages load or return a successful response without requiring login credentials
  4. Check for unauthenticated API exposure
    If the plugin exposes REST API endpoints (e.g., /wp-json/delucks/v1/* or /wp-admin/admin-ajax.php?action=delucks*), attempt to call these endpoints without authentication.
    Affected if API endpoints respond successfully to unauthenticated requests and return SEO configuration data or allow settings changes

You are affected if the Delucks SEO plugin version is below 2.5.5 and sensitive SEO configuration functions or admin pages are accessible without proper authorization credentials.

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
Upgrade available Upgrade to 2.5.5 or later
Fixed in 2.5.5
Interim mitigation

Implement proper role-based access control (RBAC) and authorization checks on all sensitive endpoints and administrative functions within the plugin.

Recommended fix Moderate confidence

2.5.5

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find Delucks SEO in the plugin list
  4. Check if an update is available (current version should show as < 2.5.5)
  5. Click 'Update Now' to upgrade to version 2.5.5
  6. Alternatively, download version 2.5.5 from the official WordPress plugin repository or vendor
  7. Navigate to Plugins > Add New > Upload Plugin
  8. Upload the Delucks SEO 2.5.5 zip file and install

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

Fix this in Delucks Seo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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