LiveActive security incident?Get immediate response
CVE Record

CVE-2024-24798: WordPress Debug Plugin <= 1.10 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in SoniNow Team Debug.This issue affects Debug: from n/a through 1.10.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-24798 is a CSRF flaw in the WordPress Debug plugin by SoniNow Team through version 1.10. An attacker could trick a logged-in user into performing an unintended action, causing limited integrity impact. The sources do not show confirmed exploitation or a named fixed version.

Executive priority

Treat as a routine but real WordPress plugin risk. It is not currently supported by the supplied evidence as actively exploited, but affected sites should be inventoried and remediated during normal vulnerability management cycles.

Technical view

The issue is CWE-352 Cross-Site Request Forgery affecting SoniNow Team Debug for WordPress from unspecified earlier versions through 1.10. CVSS 3.1 is 4.3, with network attack vector, low complexity, no attacker privileges, required user interaction, unchanged scope, and low integrity impact only.

Likely exposure

Exposure is likely limited to WordPress sites that have the Debug plugin installed at version 1.10 or earlier. Risk depends on whether an attacker can induce a privileged or relevant logged-in user to interact with attacker-controlled content.

Exploitation context

The provided bundle says KEV is false and contains no cited evidence of active exploitation. The CVSS vector requires user interaction, so exploitation would depend on social engineering rather than unauthenticated direct compromise.

Researcher notes

Evidence is sparse: the CVE identifies CSRF and affected range through 1.10, but the bundle does not describe the vulnerable action, endpoint, nonce failure, exploit activity, or a fixed version. Avoid assuming impact beyond low integrity without vendor details.

Mitigation direction

  • Inventory WordPress sites for the Debug plugin and record installed versions.
  • If version is 1.10 or earlier, check vendor or Patchstack guidance for a fixed release.
  • Update if a vendor-fixed version is available through trusted WordPress channels.
  • Disable or remove the plugin where it is not operationally required.
  • Apply normal WordPress hardening and limit administrative browsing from logged-in sessions.

Validation and detection

  • Confirm whether each WordPress site has the Debug plugin installed.
  • Verify the installed plugin version is not 1.10 or earlier.
  • Check Patchstack and CVE records for any updated remediation status.
  • Review change records to confirm update, disablement, or removal was completed.
  • Re-scan plugin inventory after remediation to confirm exposure is cleared.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-24798 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2024-24798Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SoniNow TeamDebugdebug, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.