CVE-2026-10698
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 · uneditedImproper Neutralization of Special Elements in Data Query Logic vulnerability in Progress MOVEit Transfer (Custom Reports modules). This issue affects MOVEit Transfer: from 2025.0.0 before 2025.0.8, from 2025.1.0 before 2025.1.4, from 2026.0.0 before 2026.0.1.
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 confidenceSQL injection vulnerability (CWE-89) in the Custom Reports module of MOVEit Transfer allows attackers to inject malicious SQL commands through improper neutralization of special elements in data query logic. Successful exploitation could enable unauthorized database access, data exfiltration, or potential privilege escalation.
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<= 2024.1.8>= 2025.0.0, < 2025.0.8>= 2025.1.0, < 2025.1.4= 2026.0.0CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify MOVEit Transfer versionAccess the MOVEit Transfer admin interface and navigate to Help > About, or check the installation documentation for the version location in the system information panelAffected if The version displayed is <= 2024.1.8, between 2025.0.0 and 2025.0.7 inclusive, between 2025.1.0 and 2025.1.3 inclusive, or exactly 2026.0.0
-
Confirm Custom Reports module statusIn the MOVEit Transfer admin interface, navigate to System > Modules or Features settings and locate the Custom Reports module entry to verify whether it is enabled or disabledAffected if The Custom Reports module is listed as enabled or active
-
Check for recent module access logsReview MOVEit Transfer audit logs or module access logs for any recent activity involving the Custom Reports feature, typically found in the administrative logging or monitoring sectionAffected if Custom Reports module access is logged, indicating the module is functional and potentially reachable
A user is affected if their MOVEit Transfer version falls within the vulnerable ranges AND the Custom Reports module is enabled or accessible in their environment.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2025.0.82025.1.4
Apply vendor-supplied patches: upgrade to 2025.0.8, 2025.1.4, 2026.0.1 or later. If immediate patching is not feasible, restrict or disable the Custom Reports module until the patch can be applied.
2025.0.8, 2025.1.4, or 2026.0.1 (depending on your current major version branch)
- Identify your current MOVEit Transfer version from the admin console or installation
- If running 2025.0.x: Upgrade to version 2025.0.8 or later
- If running 2025.1.x: Upgrade to version 2025.1.4 or later
- If running 2026.0.0: Upgrade to version 2026.0.1 or later
- If running 2024.1.8 or earlier: Contact Progress Software directly for available patches or upgrade options, as no specific fixed version is documented for this branch
- After upgrade, verify the Custom Reports module is functioning correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10698 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-10698 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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