CVE-2025-7388
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 · uneditedIt was possible to perform Remote Command Execution (RCE) via Java RMI interface in the OpenEdge AdminServer, allowing authenticated users to inject and execute OS commands under the delegated authority of the AdminServer process. An RMI interface permitted manipulation of a configuration property with inadequate input validation leading to OS command injection.
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 confidenceOpenEdge AdminServer contains a Java RMI interface with inadequate input validation on a configuration property, allowing authenticated attackers to inject and execute OS commands under the privileges of the AdminServer process. This is a command injection vulnerability in the RMI layer.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L
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 if OpenEdge AdminServer is installedLook for OpenEdge installation directories (typically under /opt progress or C:\Progress on Windows) and check for the AdminServer component. On Unix systems, check for processes named 'adminServer' or 'oeadmin'. On Windows, check services named 'OpenEdge AdminServer'.Affected if OpenEdge AdminServer is found running on the system
-
Check AdminServer versionRun the OpenEdge version command (oeprompt or pro -version) from the installation bin directory, or check the adminhub or opensrf.xml configuration files for version strings. Compare against any available patch level information.Affected if The installed version has not received the vendor patch for CVE-2025-7388
-
Verify RMI interface is configuredCheck the OpenEdge admin server configuration (typically in the adminserver or openedge directory) for RMI-related settings. Look for rmi.port or java.rmi settings in configuration files. Confirm the RMI service is active by checking if the configured RMI port (commonly 20931 or 20932) is listening.Affected if The RMI interface is enabled and the port is listening/accessible
-
Check network exposure of AdminServerReview firewall rules and network configuration to determine if the AdminServer RMI port is accessible from untrusted networks. Use netstat or similar tools to identify bound IP addresses for the RMI port.Affected if The AdminServer RMI port is accessible from network segments outside the trusted administrative zone
-
Review admin server logs for suspicious activityExamine OpenEdge AdminServer logs (typically in the adminserver logs directory) for unusual command patterns, unexpected authentication events, or suspicious RMI invocations around the time window of potential exploitation.Affected if Logs contain unexpected commands, unfamiliar authenticated sessions, or evidence of RMI abuse
A user is affected if OpenEdge AdminServer is running with an unpatched version and the RMI interface is accessible, regardless of whether authentication credentials are known to the defender.
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.
From vendor dataApply vendor patches for OpenEdge AdminServer when available. Until then, restrict AdminServer access to only trusted authenticated users and network access via firewalling/segmentation.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7388 — 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-2025-7388 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