LiveActive security incident?Get immediate response
CVE Record

CVE-2024-25910: WordPress MoveTo Plugin <= 6.2 is vulnerable to SQL Injection

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Skymoonlabs MoveTo.This issue affects MoveTo: from n/a through 6.2.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2024-25910 is a critical SQL injection issue in the WordPress MoveTo plugin through version 6.2. A public website using this plugin could expose site data and integrity if attacked. The source bundle does not show confirmed active exploitation or a named fixed version.

Executive priority

Handle as urgent for any production WordPress site using MoveTo through 6.2. The issue is critical and unauthenticated by scoring, but current sources do not prove exploitation in the wild.

Technical view

The CVE describes CWE-89 improper SQL command neutralization in Skymoonlabs MoveTo through 6.2. CVSS 3.1 is 9.8: network-accessible, low complexity, unauthenticated, no user interaction, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely limited to WordPress installations with Skymoonlabs MoveTo installed at version 6.2 or earlier. Public internet-facing WordPress sites have the highest business risk. The source bundle provides no CPEs and does not identify other affected products.

Exploitation context

The CVSS vector indicates unauthenticated remote attack potential, but the bundle does not provide exploit details. KEV is false, and no cited source in the bundle confirms active exploitation. Treat as urgent based on severity, not proven exploitation.

Researcher notes

The public bundle does not include vulnerable parameter names, affected code paths, exploitability proof, or a fixed version. Validation should focus on asset inventory, version confirmation, exposure, telemetry review, and vendor guidance tracking without assuming details absent from sources.

Mitigation direction

  • Inventory WordPress sites for the MoveTo plugin and installed version.
  • Disable or remove MoveTo where business impact allows until vendor guidance is confirmed.
  • Check Patchstack, CVE, and vendor channels for a supported fixed release.
  • Prioritize internet-facing and high-value WordPress sites first.
  • Review database backups and recovery readiness for affected sites.

Validation and detection

  • Confirm whether MoveTo is installed on each WordPress instance.
  • Record plugin versions and flag any version through 6.2.
  • Review web and database logs for unusual query errors or data access patterns.
  • Check whether any compensating WAF or virtual patching is enabled.
  • Document remediation status for each affected WordPress site.
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-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. 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
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-25910 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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
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
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2024-25910Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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
SkymoonlabsMoveTon/aunaffected
Weakness

CWE details

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

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.