dbcve.org
DarkmysiteWordPress extension

CVE-2024-50466

HIGH · 8.8 CVSS v3.1 Published 2024-10-29
Fix available
A fix is available. Upgrade to after 1.2.8 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in DarkMySite DarkMySite – Advanced Dark Mode Plugin for WordPress darkmysite allows Cross Site Request Forgery.This issue affects DarkMySite – Advanced Dark Mode Plugin for WordPress: from n/a through 1.2.8.

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

Cross-Site Request Forgery (CSRF) vulnerability in the DarkMySite WordPress plugin allows attackers to induce authenticated users to perform unintended actions by tricking them into visiting malicious pages. The plugin fails to properly validate anti-CSRF tokens (nonces) on sensitive operations, enabling attackers to execute administrative actions on behalf of logged-in administrators.

MitigationImplement WordPress nonces (wp_create_nonce, wp_verify_nonce) on all form submissions and AJAX requests within the plugin to validate request origin and intent. Verify the nonce before processing any state-changing operations.

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
DarkmysiteWordPress extension
Affected:<= 1.2.8

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Verify DarkMySite plugin is installed
    Log into WordPress admin dashboard, navigate to Plugins > Installed Plugins, and locate DarkMySite in the list. Note its activation status.
    Affected if Plugin is not installed or not activated - no CSRF risk from this plugin
  2. Determine installed version
    In the Plugins list, view the plugin details or check the plugin header in /wp-content/plugins/darkmysite/darkmysite.php for the 'Version' defined in the plugin comment block.
    Affected if Version is 1.2.8 or lower - vulnerable to CVE-2024-50466
  3. Inspect sensitive operations for nonce validation
    Examine PHP files in the plugin directory (especially files handling form submissions and AJAX actions) for presence of wp_verify_nonce, check_admin_referer, or wp_create_nonce calls before processing state-changing operations.
    Affected if Sensitive admin actions lack nonce verification - the CSRF vulnerability is present and exploitable

Environment is affected if DarkMySite plugin is installed with version 1.2.8 or lower and the plugin code does not validate nonces on sensitive operations.

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 a release after 1.2.8
Interim mitigation

Implement WordPress nonces (wp_create_nonce, wp_verify_nonce) on all form submissions and AJAX requests within the plugin to validate request origin and intent. Verify the nonce before processing any state-changing operations.

Recommended fix Moderate confidence

Latest available version of DarkMySite plugin (after 1.2.8) from wordpress.org plugin repository

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the DarkMySite plugin in the list
  4. Check if an update is available for the DarkMySite plugin
  5. If an update is available, click 'Update Now' to install the latest version
  6. If no update is visible in WordPress, manually download the latest version from the official WordPress plugin repository (wordpress.org/plugins) and upload it via Plugins > Add New > Upload Plugin, replacing the existing installation
  7. After updating, verify the plugin is functioning correctly on the site

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

Fix this in Darkmysite Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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