← Back

Openmeetings

openmeetings

Vendor: Apache • 29 CVEs

CVEs (29)

CVE
VENDORS
PRODUCTS
UPDATED
PUBLISHED
CVSS
1Apache
1Openmeetings
Jul 15, 2026
Jul 14, 2026
N/A· v4
6.5 MEDIUM· v3
N/A· v2
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Apache OpenMeetings. This issue affects Apache OpenMeetings: from 5.0.0 before 9.1.0. An attacker with moderator rights in...Show more
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Apache OpenMeetings. This issue affects Apache OpenMeetings: from 5.0.0 before 9.1.0. An attacker with moderator rights in any room can read arbitrary files accessible to the OS account running the OM server, including credentials and secrets, via a crafted download request. Users are recommended to upgrade to version 9.1.0, which fixes the issue.Show less
1Apache
1Openmeetings
Jun 17, 2026
Apr 9, 2026
N/A· v4
7.5 HIGH· v3
N/A· v2
Use of GET Request Method With Sensitive Query Strings vulnerability in Apache OpenMeetings. The REST login endpoint uses HTTP GET method with username and password passed as query parameters. Please check references re...Show more
Use of GET Request Method With Sensitive Query Strings vulnerability in Apache OpenMeetings. The REST login endpoint uses HTTP GET method with username and password passed as query parameters. Please check references regarding possible impact This issue affects Apache OpenMeetings: from 3.1.3 before 9.0.0. Users are recommended to upgrade to version 9.0.0, which fixes the issue.Show less
1Apache
1Openmeetings
Jun 17, 2026
Apr 9, 2026
N/A· v4
7.5 HIGH· v3
N/A· v2
Use of Hard-coded Cryptographic Key vulnerability in Apache OpenMeetings. The remember-me cookie encryption key is set to default value in openmeetings.properties and not being auto-rotated. In case OM admin hasn't chan...Show more
Use of Hard-coded Cryptographic Key vulnerability in Apache OpenMeetings. The remember-me cookie encryption key is set to default value in openmeetings.properties and not being auto-rotated. In case OM admin hasn't changed the default encryption key, an attacker who has stolen a cookie from a logged-in user can get full user credentials. This issue affects Apache OpenMeetings: from 6.1.0 before 9.0.0. Users are recommended to upgrade to version 9.0.0, which fixes the issue.Show less
1Apache
1Openmeetings
Jun 17, 2026
Apr 9, 2026
N/A· v4
4.3 MEDIUM· v3
N/A· v2
Improper Handling of Insufficient Privileges vulnerability in Apache OpenMeetings. Any registered user can query web service with their credentials and get files/sub-folders of any folder by ID (metadata only NOT conten...Show more
Improper Handling of Insufficient Privileges vulnerability in Apache OpenMeetings. Any registered user can query web service with their credentials and get files/sub-folders of any folder by ID (metadata only NOT contents). Metadata includes id, type, name and some other field. Full list of fields get be checked at FileItemDTO object. This issue affects Apache OpenMeetings: from 3.10 before 9.0.0. Users are recommended to upgrade to version 9.0.0, which fixes the issue.Show less
1Apache
1Openmeetings
Jun 17, 2026
Jan 8, 2025
N/A· v4
9.8 CRITICAL· v3
N/A· v2
Vendor: The Apache Software Foundation Versions Affected: Apache OpenMeetings from 2.1.0 before 8.0.0 Description: Default clustering instructions at https://openmeetings.apache.org/Clustering.html  doesn't specify wh...Show more
Vendor: The Apache Software Foundation Versions Affected: Apache OpenMeetings from 2.1.0 before 8.0.0 Description: Default clustering instructions at https://openmeetings.apache.org/Clustering.html  doesn't specify white/black lists for OpenJPA this leads to possible deserialisation of untrusted data. Users are recommended to upgrade to version 8.0.0 and update their startup scripts to include the relevant 'openjpa.serialization.class.blacklist' and 'openjpa.serialization.class.whitelist' configurations as shown in the documentation.Show less
1Apache
1Openmeetings
Jun 17, 2026
May 12, 2023
N/A· v4
7.2 HIGH· v3
N/A· v2
An attacker who has gained access to an admin account can perform RCE via null-byte injection Vendor: The Apache Software Foundation Versions Affected: Apache OpenMeetings from 2.0.0 before 7.1.0
1Apache
1Openmeetings
Jun 17, 2026
May 12, 2023
N/A· v4
8.1 HIGH· v3
N/A· v2
An attacker that has gained access to certain private information can use this to act as other user. Vendor: The Apache Software Foundation Versions Affected: Apache OpenMeetings from 3.1.3 before 7.1.0
1Apache
1Openmeetings
Jun 17, 2026
May 12, 2023
N/A· v4
5.3 MEDIUM· v3
N/A· v2
Attacker can access arbitrary recording/room Vendor: The Apache Software Foundation Versions Affected: Apache OpenMeetings from 2.0.0 before 7.1.0
1Apache
1Openmeetings
Jun 17, 2026
Mar 28, 2023
N/A· v4
9.8 CRITICAL· v3
N/A· v2
Vendor: The Apache Software Foundation Versions Affected: Apache OpenMeetings from 2.0.0 before 7.0.0 Description: Attacker can elevate their privileges in any room
1Apache
1Openmeetings
Jun 17, 2026
Mar 15, 2021
N/A· v4
7.5 HIGH· v3
5.0 MEDIUM· v2
If was found that the NetTest web service can be used to overload the bandwidth of a Apache OpenMeetings server. This issue was addressed in Apache OpenMeetings 6.0.0
1Apache
1Openmeetings
Jun 17, 2026
Sep 30, 2020
N/A· v4
7.5 HIGH· v3
5.0 MEDIUM· v2
Attackers can use public NetTest web service of Apache OpenMeetings 4.0.0-5.0.0 to organize denial of service attack.
1Apache
1Openmeetings
Nov 21, 2024
Feb 28, 2018
N/A· v4
6.5 MEDIUM· v3
4.0 MEDIUM· v2
In Apache OpenMeetings 3.0.0 - 4.0.1, CRUD operations on privileged users are not password protected allowing an authenticated attacker to deny service for privileged users.
1Apache
1Openmeetings
May 13, 2026
Oct 12, 2017
N/A· v4
9.8 CRITICAL· v3
7.5 HIGH· v2
Apache OpenMeetings before 3.1.2 is vulnerable to Remote Code Execution via RMI deserialization attack.
1Apache
1Openmeetings
May 13, 2026
Jul 17, 2017
N/A· v4
7.5 HIGH· v3
5.0 MEDIUM· v2
Apache OpenMeetings 1.0.0 updates user password in insecure manner.
1Apache
1Openmeetings
May 13, 2026
Jul 17, 2017
N/A· v4
5.3 MEDIUM· v3
5.0 MEDIUM· v2
Apache OpenMeetings 1.0.0 responds to the following insecure HTTP methods: PUT, DELETE, HEAD, and PATCH.
1Apache
1Openmeetings
May 13, 2026
Jul 17, 2017
N/A· v4
7.5 HIGH· v3
5.0 MEDIUM· v2
Apache OpenMeetings 1.0.0 doesn't check contents of files being uploaded. An attacker can cause a denial of service by uploading multiple large files to the server.
1Apache
1Openmeetings
May 13, 2026
Jul 17, 2017
N/A· v4
7.5 HIGH· v3
5.0 MEDIUM· v2
Apache OpenMeetings 1.0.0 displays Tomcat version and detailed error stack trace, which is not secure.
1Apache
1Openmeetings
May 13, 2026
Jul 17, 2017
N/A· v4
8.2 HIGH· v3
6.4 MEDIUM· v2
Apache OpenMeetings 3.2.0 is vulnerable to parameter manipulation attacks, as a result attacker has access to restricted areas.
1Apache
1Openmeetings
May 13, 2026
Jul 17, 2017
N/A· v4
8.8 HIGH· v3
6.5 MEDIUM· v2
Apache OpenMeetings 1.0.0 is vulnerable to SQL injection. This allows authenticated users to modify the structure of the existing query and leak the structure of other queries being made by the application in the back-en...Show more
Apache OpenMeetings 1.0.0 is vulnerable to SQL injection. This allows authenticated users to modify the structure of the existing query and leak the structure of other queries being made by the application in the back-end.Show less
1Apache
1Openmeetings
May 13, 2026
Jul 17, 2017
N/A· v4
7.5 HIGH· v3
5.0 MEDIUM· v2
Apache OpenMeetings 1.0.0 has an overly permissive crossdomain.xml file. This allows for flash content to be loaded from untrusted domains.