dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2024-11415

HIGH · 8.8 CVSS v3.1 Published 2024-11-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
The WP-Orphanage Extended plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.2. This is due to missing or incorrect nonce validation on the wporphanageex_menu_settings() function. This makes it possible for unauthenticated attackers to escalate the privileges of all orphan accounts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 · high confidence

The WP-Orphanage Extended WordPress plugin fails to validate anti-CSRF nonces in the wporphanageex_menu_settings() function, allowing unauthenticated attackers to forge requests that modify settings. By tricking an administrator into clicking a malicious link, attackers can escalate privileges of orphan accounts on the WordPress site.

MitigationUpdate the plugin to a version beyond 1.2 that includes proper nonce validation, or implement nonce checks in the wporphanageex_menu_settings() function before processing any settings changes.

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
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. Locate the WP-Orphanage Extended plugin installation
    Navigate to your WordPress wp-content/plugins/ directory and search for a folder named 'wp-orphanage-extended', 'wp-orphanageex', or similar variant containing 'orphanage' in the name. Alternatively, check the Plugins section in the WordPress admin dashboard.
    Affected if The plugin is not found in the plugins directory or not listed in the admin panel, the site is not affected by this CVE.
  2. Identify the installed plugin version
    If the plugin is found, open its main PHP file (usually named the same as the plugin folder, e.g., wp-orphanageex.php) and locate the version comment or header. Alternatively, in the WordPress admin, go to Plugins > Installed Plugins and find the version number listed for WP-Orphanage Extended.
    Affected if The version is 1.2 or lower, or if no version can be determined and the plugin contains the vulnerable function, the site may be affected.
  3. Locate the wporphanageex_menu_settings function
    Search the plugin's PHP files for the string 'function wporphanageex_menu_settings'. This function is located in the plugin's main file or an included settings file.
    Affected if The function does not exist in the codebase, the vulnerability is not present.
  4. Verify nonce validation in the vulnerable function
    Open the file containing wporphanageex_menu_settings and examine the function. Look for WordPress nonce verification calls such as 'wp_verify_nonce', 'check_admin_referer', or 'check_ajax_referer' before any settings processing or database update operations.
    Affected if The function lacks nonce validation checks (the nonce verification is missing, commented out, or only present without being enforced), the site is vulnerable to CVE-2024-11415.

If the WP-Orphanage Extended plugin is installed, the installed version is 1.2 or lower, and the wporphanageex_menu_settings function lacks proper nonce verification, the environment is affected by this CSRF 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.

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

Update the plugin to a version beyond 1.2 that includes proper nonce validation, or implement nonce checks in the wporphanageex_menu_settings() function before processing any settings changes.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (version 1.3 or higher)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the WP-Orphanage Extended plugin
  4. Check the current installed version - if it is 1.2 or earlier, an update is needed
  5. Update the plugin to the latest available version from the WordPress plugin repository

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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