dbcve.org
DebugWordPress extension · Soninow

CVE-2024-24798

HIGH · 8.8 CVSS v3.1 Published 2024-02-21
Fix available
A fix is available. Upgrade to 1.11 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 SoniNow Team Debug.This issue affects Debug: from n/a through 1.10.

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

Cross-Site Request Forgery (CSRF) vulnerability in SoniNow Team Debug plugin versions through 1.10. The plugin lacks proper anti-CSRF token validation on state-changing actions, allowing attackers to trick authenticated administrators into performing unintended debug-related operations via malicious links or forms.

MitigationImplement WordPress nonces (anti-CSRF tokens) on all forms and AJAX actions within the Debug plugin, and validate the nonce on all server-side processing. Add SameSite attribute to session cookies and verify Origin/Referer headers as additional defense.

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
DebugWordPress extension
Affected:< 1.11

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 SoniNow Debug plugin installation
    Check your WordPress site's wp-content/plugins/ directory for a folder named 'soninow-debug' or similar, or query the WordPress database in the wp_options table for the plugin option containing 'soninow' and 'debug'.
    Affected if The plugin folder exists in wp-content/plugins/ or the plugin is listed in WordPress active plugins.
  2. Determine installed plugin version
    Open the main plugin PHP file (typically soninow-debug.php or index.php inside the plugin folder) and locate the version defined in the plugin header comment, or check the Version entry in the plugin's readme.txt file.
    Affected if The version number is 1.10 or lower, or if no version is displayed and the plugin has not been updated since the CVE disclosure date.
  3. Verify WordPress nonces are implemented on plugin forms
    Search the plugin's PHP files for occurrences of 'wp_nonce_field', 'wp_create_nonce', or 'check_admin_referer' functions. Inspect the main PHP files handling form submissions (usually in admin/ or includes/ folders within the plugin).
    Affected if No nonce-related function calls are found in files that handle form submissions or state-changing actions, or if nonces exist but are not validated before processing.
  4. Check AJAX actions for nonce validation
    Examine PHP files registering AJAX hooks (search for 'add_action' with 'wp_ajax_') and verify that each callback includes nonce verification using 'check_ajax_referer' or 'wp_verify_nonce'.
    Affected if AJAX endpoints registered by the plugin do not include nonce validation checks before executing their callback functions.

You are affected if the SoniNow Debug plugin is installed at version 1.10 or below AND the plugin's forms or AJAX actions lack proper WordPress nonce validation.

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 1.11 or later
Fixed in 1.11
Interim mitigation

Implement WordPress nonces (anti-CSRF tokens) on all forms and AJAX actions within the Debug plugin, and validate the nonce on all server-side processing. Add SameSite attribute to session cookies and verify Origin/Referer headers as additional defense.

Recommended fix Moderate confidence

1.11

  1. 1. Backup your WordPress site before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. 3. Locate the Debug plugin by SoniNow Team
  4. 4. If an update is available, click 'Update Now' to upgrade to version 1.11 or later
  5. 5. Verify the plugin version after update to confirm version 1.11 is installed
  6. 6. Test that the plugin functionality works as expected after the upgrade

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

Fix this in Debug 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-24798 — 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-24798 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