VulnerabilityPublished 18 Jan 2024Updated 2 Jun 2025

CVE-2023-40051: Progress Software OpenEdge · Unrestricted File Upload

Affects Progress Software OpenEdgeSource CVE Database V5

Not known to be exploited · CVSS 9.1 Critical · fixed in 12.8.0 : patch Progress Software OpenEdge as a priority.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

9.1Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 12.8.0, 12.2.13, 11.7.18

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: Low
Integrity: High
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade com.progress/openedge to 12.8.0, 12.2.13 or 11.7.18.

Affected software

Product	Affected	Fixed in
Mavencom.progress/openedge`pkg:maven/com.progress/openedge`Other threats	Affected <11.7.18 <12.2.13 <12.8.0	Fixed in 11.7.18 12.2.13 12.8.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Immediate patching: Organizations should promptly update PASOE to versions 11.7.18, 12.2.13, or later innovation releases where the vulnerability is addressed.
Restrict file upload permissions: Implement strict access controls on directories used by PASOE for file uploads, ensuring only authorized processes and users can write or execute files.
Web transport configuration: Review and harden the configuration of the WEB transport component to limit or disable file upload capabilities if not required by business processes.
Input validation and filtering: Deploy application-layer controls or web application firewalls (WAFs) to detect and block suspicious file upload attempts, particularly those with executable or script extensions.
Network segmentation: Isolate PASOE servers within secure network zones to limit lateral movement in case of compromise.
Monitoring and logging: Enable detailed logging of file upload activities and monitor for anomalous patterns indicative of exploitation attempts.
Incident response readiness: Prepare and test response plans for potential exploitation scenarios involving unauthorized file uploads.
Vendor communication: Maintain active communication with Progress Software for updates, patches, and advisories related to this vulnerability.

Description

This issue affects Progress Application Server (PAS) for OpenEdge in versions 11.7 prior to 11.7.18, 12.2 prior to 12.2.13, and innovation releases prior to 12.8.0. An attacker can formulate a request for a WEB transport that allows unintended file uploads to a server directory path on the system running PASOE. If the upload contains a payload that can further exploit the server or its network, the launch of a larger scale attack may be possible.

Impact

For European organizations, the impact of CVE-2023-40051 can be substantial, especially for those relying on Progress OpenEdge for critical business applications, including ERP, financial systems, and supply chain management. Successful exploitation could lead to unauthorized modification of application data (high integrity impact), potentially causing data corruption, fraud, or operational disruption. The ability to upload malicious files may also facilitate the deployment of malware or ransomware, threatening availability and business continuity. Given the network-exploitable nature and no requirement for user interaction, attackers could remotely compromise systems, increasing the risk of widespread infection within enterprise networks. This is particularly concerning for sectors with stringent data protection requirements under GDPR, as any breach involving personal or sensitive data could result in regulatory penalties and reputational damage. Additionally, the vulnerability could be leveraged as an initial foothold in targeted attacks against European organizations, especially those in manufacturing, finance, and public sectors where OpenEdge deployments are common. The absence of known exploits currently provides a window for proactive defense, but the critical severity score underscores the urgency of mitigation.

CWE-434Unrestricted Upload of File with Dangerous Type (opens in a new tab)
Base weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #12OWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product allows the upload or transfer of dangerous file types that are automatically processed within its environment.
Architecture and Design
Generate a new, unique filename for an uploaded file instead of using the user-supplied filename, so that no external input is used at all.
Architecture and Design · Enforcement by Conversion
When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
Architecture and Design
Consider storing the uploaded files outside of the web document root entirely. Then, use other mechanisms to deliver the files dynamically.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Web Service Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
File Upload (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V12.5.2 (opens in a new tab)
V13.1.5 (opens in a new tab)
V12.2.1 (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Jul 2025, 17:27 UTC

WeaknessesCWE-434

Technical details

References

Community reviews

Related threats