LiveActive security incident?Get immediate response
CVE Record

CVE-2024-0428: Index Now <= 2.6.3 - Cross-Site Request Forgery via reset_form

The Index Now plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.6.3. This is due to missing or incorrect nonce validation on the 'reset_form' function. This makes it possible for unauthenticated attackers to delete arbitrary site options via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2024-0428 is a WordPress plugin CSRF issue. If an administrator is tricked into taking an action, an unauthenticated attacker could cause deletion of site options. That can disrupt site behavior or availability, but the sources do not show data theft or confirmed active exploitation.

Executive priority

Treat as a high-priority website reliability risk where the plugin is present. It needs prompt patch validation, but urgency is lower than remotely exploitable flaws with confirmed active exploitation.

Technical view

The flaw is missing or incorrect nonce validation in the Index Now plugin reset_form function through version 2.6.3. The reported impact is arbitrary site option deletion via a forged administrator request. CVSS 3.1 is 7.1, with low integrity impact and high availability impact.

Likely exposure

Likely exposure is WordPress sites running Index Now up to 2.6.3. The bundle’s affected-product metadata is inconsistent with the title and description, so teams should confirm the installed plugin slug, name, and version before scoping.

Exploitation context

The CVE is not listed in KEV, and the provided sources do not cite active exploitation. Exploitation requires user interaction by a site administrator, such as following a malicious link while authenticated.

Researcher notes

Primary uncertainty is product metadata: the narrative identifies Index Now through 2.6.3, while the affected entry names a different product and marks default status unaffected. Base validation on actual plugin slug/version and the referenced WordPress changeset.

Mitigation direction

  • Update the affected WordPress plugin to version 2.6.4 or later where applicable.
  • Confirm vendor guidance before applying fixes if plugin identity differs in inventory.
  • Restrict administrator browsing from untrusted links and external content.
  • Review recent unexpected WordPress option changes or configuration resets.

Validation and detection

  • Inventory WordPress sites for the Index Now plugin and installed version.
  • Confirm whether any installation is at or below version 2.6.3.
  • Check vendor or WordPress.org changelog references for the 2.6.4 fix.
  • Review admin activity around unexpected setting or option changes.
Prepared
Confidence
medium
Sources
4

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-0428 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
High
CVSS
7.1 (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:H

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
3Source 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
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H2.84.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2024-0428Attack 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:H

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
properfractionCrawlWP SEO – Instant Search Engine Indexing & SEO Performance Monitor0unaffected
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.