What is CVE-2023-34362?

CVE-2023-34362 is Progress MOVEit Transfer SQL Injection Vulnerability. The supplied enrichment data classifies it as Injection mapped to CWE-89 SQL Injection.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Yes. The supplied enrichment data lists CVE-2023-34362 in CISA KEV with required action: Apply updates per vendor instructions.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

1104 public PoC repositories reported; 3 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS, database audit logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2023-34362 using CVSS 9.8, EPSS 100%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

Publicly linked actor or ransomware signals in the supplied enrichment data: RomCom (), Kimsuky (), APT37 (), TA505 (), Silence group (), Ransomware use: Known. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVRansomwarecriticalInjectionpublic exploit

CVE-2023-34362

CVE-2023-34362 — Progress MOVEit Transfer SQL Injection Vulnerability

In Progress MOVEit Transfer before 2021.0.6 (13.0.6), 2021.1.4 (13.1.4), 2022.0.4 (14.0.4), 2022.1.5 (14.1.5), and 2023.0.1 (15.0.1), a SQL injection vulnerability has been found in the MOVEit Transfer web application that could allow an unauthenticated attacker to gain access to MOVEit Transfer's database. Depending on the database engine being used (MySQL, Microsoft SQL Server, or Azure SQL), an attacker may be able to infer information about the structure and contents of the database, and execute SQL statements that alter or delete database elements. NOTE: this is exploited in the wild in May and June 2023; exploitation of unpatched systems can occur via HTTP or HTTPS. All versions (e.g., 2020.0 and 2019x) before the five explicitly mentioned versions are affected, including older unsupported versions.

Published Jun 2, 2023Updated Jun 17, 2026Sources: NVD, Progress (CNA), CISA, FIRST EPSS, GitHub, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Jun 2, 2023

EPSS

100%

top of FIRST's scoreset

Affects

Progress

MOVEit Transfer

CVSS base

9.8

critical

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade MOVEit Transfer to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

CISA required action

Apply updates per vendor instructions.

Federal deadline Jun 23, 2023 — passed 1,179 days ago

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
Progress	MOVEit Transfer	—	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
9.8	CVSS 3.1	critical	3.9	5.9	NVD, CNA

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

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Read Application Data
Bypass Protection Mechanism
Modify Application Data

Mitigation: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using persistence layers such as Hibernate or Enterprise Java Beans, which can provide significant protection against SQL injection if used properly.

Weakness & attack patterns

CWE-89SQL Injection

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-470 · Expanding Control over the Operating System from the DatabaseCAPEC-109 · Object Relational Mapping InjectionCAPEC-110 · SQL Injection through SOAP Parameter TamperingCAPEC-7 · Blind SQL InjectionCAPEC-108 · Command Line Execution through SQL InjectionCAPEC-66 · SQL Injection

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Jun 2, 2023

Federal deadline

Jun 23, 2023

passed 1,179 days ago

Ransomware use

Known

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

1,092

3 of the 5 sampled are weaponized

Exploit entries

Exploit-DB and CTI exploit indexes

Malware

Families a CTI source ties to this CVE. One named, with the total it tracks.

Families tracked

Named

Akira

akira, elf.akira, win.akira

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

10 more posts on this CVEShowing 5 of 15 · Who is discussing this CVE, and how loudlyUnlock free

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable MOVEit Transfer.
Monitor for scanner or exploit-pattern traffic after 1104 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPSdatabase audit logs

Exposure queries

Search-engine queries that surface exposed instances. Run them against your own estate first.

http.html:MOVEit
http.favicon.hash:989289239
http.favicon.hash:-662184115

Groups associated with this CVE

Groups reported in connection with this vulnerability. A reported association, not a confirmed observation of that group using it — and not scoped to any sector or campaign.

RomComKimsukyAPT37TA505Silence group

19 more threat groups on this CVEShowing 5 of 24 · Attribution, campaigns and the malware each one runsUnlock free

ip5.188.87.4020
Maltrail Malware Feeds · Sep 25, 2024
ip45.182.189.22836
Pulse Dive IP Addresses · Apr 9, 2023
ip88.214.27.10137
Kaspersky Public Requests · Dec 10, 2022
ip46.161.27.15535
AlienVault OTX Feeds · Sep 3, 2022
ip179.60.149.24445
Maltrail Malware Feeds · Sep 26, 2023

5 more indicators on this CVEShowing 5 of 10 · Hashes, addresses and domains from a live threat exchangeUnlock free

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 9.8 (AV:N)
Jun 17, 2026 · NVD
Cve is exploited KarmanyaT28/Multi-Stage-Exploitation-and-Detection-Engineering-Analysis-of-CVE-2023-34362-in-MOVEit-Transfer
May 7, 2026 · SOCRadar CTI
2023
Added to CISA KEV catalog
Jun 2, 2023 · CISA
Initial · CVE published
Jun 2, 2023 · NVD

Source activity

Readings a source repeats on a schedule, counted rather than listed.

16×TweetsOct 24, 2025 – Aug 26, 2026 · SOCRadar CTI
7×SVRS was changedOct 27, 2025 – Aug 24, 2026 · SOCRadar CTI
4×Github ReposJan 21, 2026 – Jun 6, 2026 · SOCRadar CTI
1×CVE appeared in the Cve Trends.Jun 26, 2026 · SOCRadar CTI

References

6 on the record

packetstormsecurity.com/files/172883/MOVEit-Transfer-SQL-Injection-Remote-Code-Execution.html
Third Party Advisory, VDB Entry, NIST, GITHUB
packetstormsecurity.com/files/173110/MOVEit-SQL-Injection.html
Exploit, Third Party Advisory, VDB Entry, NIST, GITHUB
community.progress.com/s/article/MOVEit-Transfer-Critical-Vulnerability-31May2023
Vendor Advisory, NIST
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-34362
US Government Resource
www.cisa.gov/news-events/cybersecurity-advisories/aa23-158a
US Government Resource
nvd.nist.gov/vuln/detail/CVE-2023-34362
Vendor Advisory

Coverage

14 stories from the feeds we poll

9 more reports on this CVEShowing 5 of 14 · Vendor research and security press coverageUnlock free

Elsewhere on this site

Progressevery CVE for this vendor
June 2023what else CISA listed
Injectionsame class
CWE-89other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

Only the 5 indicator(s) reported for this CVE are available; no packet-level or host-forensic artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2023-34362 is Progress MOVEit Transfer SQL Injection Vulnerability, a critical vulnerability affecting MOVEit Transfer from Progress. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 1104 public PoC repositories reported; 3 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 9.8 describes technical severity, while EPSS 100% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.