Apache Openmeetings
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in Apache Openmeetings.
By the Year
In 2026 there have been 0 vulnerabilities in Apache Openmeetings. Last year, in 2025 Openmeetings had 1 security vulnerability published. Right now, Openmeetings is on track to have less security vulnerabilities in 2026 than it did last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 0 | 0.00 |
| 2025 | 1 | 9.80 |
| 2024 | 0 | 0.00 |
| 2023 | 4 | 7.60 |
| 2022 | 0 | 0.00 |
| 2021 | 1 | 7.50 |
| 2020 | 1 | 7.50 |
| 2019 | 0 | 0.00 |
| 2018 | 1 | 6.50 |
It may take a day or so for new Openmeetings vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Apache Openmeetings Security Vulnerabilities
Apache OpenMeetings 2.1.0<8.0.0 Untrusted Deserialization via OpenJPA
CVE-2024-54676
9.8 - Critical
- January 08, 2025
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.
Marshaling, Unmarshaling
Apache OpenMeetings RCE through NULL-BYTE Injection (2.0.07.0.x)
CVE-2023-29246
7.2 - High
- May 12, 2023
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
Improper Input Validation
Apache OpenMeetings 3.1.37.1.0 PE Impersonate User
CVE-2023-29032
8.1 - High
- May 12, 2023
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
authentification
Arbitrary Recording Access in Apache OpenMeetings <7.1.0
CVE-2023-28936
5.3 - Medium
- May 12, 2023
Attacker can access arbitrary recording/room Vendor: The Apache Software Foundation Versions Affected: Apache OpenMeetings from 2.0.0 before 7.1.0
Incorrect Comparison
Apache OpenMeetings PrivEsc before v7.0.0
CVE-2023-28326
9.8 - Critical
- March 28, 2023
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
Missing Authentication for Critical Function
If was found that the NetTest web service can be used to overload the bandwidth of a Apache OpenMeetings server
CVE-2021-27576
7.5 - High
- March 15, 2021
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
Attackers can use public NetTest web service of Apache OpenMeetings 4.0.0-5.0.0 to organize denial of service attack.
CVE-2020-13951
7.5 - High
- September 30, 2020
Attackers can use public NetTest web service of Apache OpenMeetings 4.0.0-5.0.0 to organize denial of service attack.
In Apache OpenMeetings 3.0.0 - 4.0.1, CRUD operations on privileged users are not password protected
CVE-2018-1286
6.5 - Medium
- February 28, 2018
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.
authentification
Apache OpenMeetings 1.0.0 updates user password in insecure manner.
CVE-2017-7688
- July 14, 2017
Apache OpenMeetings 1.0.0 updates user password in insecure manner.
Apache OpenMeetings 1.0.0 responds to the following insecure HTTP methods: PUT
CVE-2017-7685
- July 14, 2017
Apache OpenMeetings 1.0.0 responds to the following insecure HTTP methods: PUT, DELETE, HEAD, and PATCH.
Apache OpenMeetings 1.0.0 doesn't check contents of files being uploaded
CVE-2017-7684
- July 14, 2017
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.
Apache OpenMeetings 1.0.0 displays Tomcat version and detailed error stack trace
CVE-2017-7683
- July 14, 2017
Apache OpenMeetings 1.0.0 displays Tomcat version and detailed error stack trace, which is not secure.
Apache OpenMeetings 3.2.0 is vulnerable to parameter manipulation attacks
CVE-2017-7682
- July 14, 2017
Apache OpenMeetings 3.2.0 is vulnerable to parameter manipulation attacks, as a result attacker has access to restricted areas.
Apache OpenMeetings 1.0.0 is vulnerable to SQL injection
CVE-2017-7681
- July 14, 2017
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.
Apache OpenMeetings 1.0.0 has an overly permissive crossdomain.xml file
CVE-2017-7680
- July 14, 2017
Apache OpenMeetings 1.0.0 has an overly permissive crossdomain.xml file. This allows for flash content to be loaded from untrusted domains.
Apache OpenMeetings 1.0.0 uses not very strong cryptographic storage
CVE-2017-7673
- July 14, 2017
Apache OpenMeetings 1.0.0 uses not very strong cryptographic storage, captcha is not used in registration and forget password dialogs and auth forms missing brute force protection.
Apache OpenMeetings 1.0.0 is vulnerable to Cross-Site Request Forgery (CSRF) attacks
CVE-2017-7666
- July 14, 2017
Apache OpenMeetings 1.0.0 is vulnerable to Cross-Site Request Forgery (CSRF) attacks, XSS attacks, click-jacking, and MIME based attacks.
Uploaded XML documents were not correctly validated in Apache OpenMeetings 3.1.0.
CVE-2017-7664
- July 14, 2017
Uploaded XML documents were not correctly validated in Apache OpenMeetings 3.1.0.
Both global and Room chat are vulnerable to XSS attack in Apache OpenMeetings 3.2.0.
CVE-2017-7663
- July 14, 2017
Both global and Room chat are vulnerable to XSS attack in Apache OpenMeetings 3.2.0.
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for Apache Openmeetings or by Apache? Click the Watch button to subscribe.