dbcve.org
OpenedgeWeb browser · Progress

CVE-2023-34203

HIGH · 8.8 CVSS v3.1 Published 2023-06-23
Fix available
A fix is available. Upgrade to 11.7.16 / 12.2.12 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
In Progress OpenEdge OEM (OpenEdge Management) and OEE (OpenEdge Explorer) before 12.7, a remote user (who has any OEM or OEE role) could perform a URL injection attack to change identity or role membership, e.g., escalate to admin. This affects OpenEdge LTS before 11.7.16, 12.x before 12.2.12, and 12.3.x through 12.6.x before 12.7.

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 confidence

In Progress OpenEdge OEM (OpenEdge Management) and OEE (OpenEdge Explorer), a URL injection vulnerability allows any authenticated remote user (with any OEM or OEE role) to manipulate their identity or role membership, enabling privilege escalation to administrative privileges. This affects OpenEdge LTS versions before 11.7.16, 12.x before 12.2.12, and 12.3.x through 12.6.x.

MitigationUpgrade OpenEdge OEM/OEE to version 12.7 or later; for LTS branches, upgrade to 11.7.16 or later, or 12.2.12 or later for 12.x branches.

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
OpenedgeWeb browser
Affected:< 11.7.16>= 12.0, < 12.2.12>= 12.3, < 12.7
Openedge ExplorerWeb browser
Affected:< 12.7
Openedge ManagementWeb browser
Affected:< 12.7

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed OpenEdge version
    Run 'openedge -version' or check the About dialog in OEM/OEE web interface, or inspect the installation manifest file typically found in the OpenEdge install directory
    Affected if The version is < 11.7.16, or >= 12.0 and < 12.2.12, or >= 12.3 and < 12.7
  2. Confirm OEM or OEE is installed
    Check for presence of OEM (OpenEdge Management) or OEE (OpenEdge Explorer) installation directories, or look for running processes named 'oemanager' or 'oemanager.exe'
    Affected if Either OEM or OEE is installed on the system
  3. Verify OEM/OEE web interface is accessible
    Attempt to access the OEM or OEE web console URL (typically on ports 8080, 9090, or configured custom ports)
    Affected if The web interface responds and accepts authentication
  4. Check for any authenticated user sessions
    Review OEM/OEE user role assignments through the administrative console or by inspecting the user configuration files in the OpenEdge install directory
    Affected if Any user accounts exist with non-administrative roles that could be exploited for privilege escalation

If OpenEdge version falls within < 11.7.16, >= 12.0 to < 12.2.12, or >= 12.3 to < 12.7 AND OEM or OEE is installed with an accessible web interface, the environment is affected by this privilege escalation vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 11.7.16 / 12.2.12 / 12.7 or later
Fixed in 11.7.1612.2.1212.7
Interim mitigation

Upgrade OpenEdge OEM/OEE to version 12.7 or later; for LTS branches, upgrade to 11.7.16 or later, or 12.2.12 or later for 12.x branches.

Recommended fix High confidence

Upgrade to OpenEdge 11.7.16 (for 11.x LTS) or OpenEdge 12.7 (for 12.x versions). For 12.0.x, minimum fixed version is 12.2.12.

  1. Identify the current OpenEdge version by checking the installation or running the version command
  2. For OpenEdge 11.x LTS versions: Plan upgrade to version 11.7.16 or later
  3. For OpenEdge 12.0.x versions: Plan upgrade to version 12.2.12 or later
  4. For OpenEdge 12.3.x through 12.6.x versions: Plan upgrade to version 12.7 or later
  5. Before upgrading, review the Progress Software release notes for any compatibility considerations
  6. Perform the upgrade following Progress documentation for your specific deployment scenario
  7. After upgrade, verify that OEM/OEE components are functioning correctly
  8. Confirm the vulnerability is remediated by reviewing the fixed version information
Caveat Review Progress OpenEdge 12.7 release notes for any compatibility changes, deprecated features, or migration requirements before upgrading.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openedge Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-34203 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-34203 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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