dbcve.org
OpenmeetingsApplication · Apache

CVE-2023-28936

MEDIUM · 5.3 CVSS v3.1 Published 2023-05-12
Fix available
A fix is available. Upgrade to 7.1.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Attacker can access arbitrary recording/room Vendor: The Apache Software Foundation Versions Affected: Apache OpenMeetings from 2.0.0 before 7.1.0

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 · moderate confidence

Access control vulnerability in Apache OpenMeetings allows unauthorized access to arbitrary recordings or rooms, likely due to improper authorization checks on resource identifiers (IDOR-like behavior).

MitigationUpgrade to Apache OpenMeetings version 7.1.0 or later to obtain the patched version.

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
OpenmeetingsApplication
Affected:>= 2.0.0, < 7.1.0

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

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

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 the installed Apache OpenMeetings version
    Locate the version information in the OpenMeetings installation, typically found in the admin dashboard under 'System' or 'About' section, or check the WAR file/version file in the installation directory
    Affected if The version cannot be determined or is not visible
  2. Compare installed version against affected range
    Check if the installed version is greater than or equal to 2.0.0 and less than 7.1.0
    Affected if The installed version falls within >= 2.0.0 and < 7.1.0
  3. Verify access controls on recordings and rooms
    Test whether users can access recordings or rooms by manipulating numeric resource identifiers in URLs or API requests, observing if authorization is properly enforced
    Affected if Unauthorized access to recordings or rooms is possible by modifying resource IDs (IDOR-like behavior)
  4. Check for recent access logs indicating anomalous recording/room access
    Review OpenMeetings access logs for requests to recordings or rooms where the user should not have permissions based on their assigned rooms or user groups
    Affected if Evidence exists of access to recordings or rooms outside the user's permitted scope

The environment is affected if Apache OpenMeetings version 2.0.0 or higher but lower than 7.1.0 is installed and unauthorized access to recordings or rooms is possible through IDOR-like manipulation of resource identifiers.

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 7.1.0 or later
Fixed in 7.1.0
Interim mitigation

Upgrade to Apache OpenMeetings version 7.1.0 or later to obtain the patched version.

Recommended fix High confidence

Apache OpenMeetings 7.1.0

  1. Backup the current Apache OpenMeetings installation, including database and configuration files
  2. Stop the running OpenMeetings service
  3. Download Apache OpenMeetings version 7.1.0 from the official Apache archives (https://archive.apache.org/dist/openmeetings/)
  4. Install or upgrade to version 7.1.0 following the standard upgrade documentation
  5. Start the OpenMeetings service
  6. Verify the installation by logging in and checking that room and recording access controls function correctly

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

Fix this in Openmeetings Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-28936 — 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-28936 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