Openmeetings vulnerabilitiesRanked by how likely they are to be used.

Product39 versions
The short answer

Openmeetings is made by Apache. We track 25 published vulnerabilities in it, across 39 versions. None of them is on the list of flaws known to be exploited today. If you run Openmeetings, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Openmeetings vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Openmeetings's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Openmeetings flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 69%

    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...

    CVSS9.8Published8 Jan 2025
  2. 69%

    Attackers can use public NetTest web service of Apache OpenMeetings 4.0.0-5.0.0 to organize denial of service attack.

    CVSS7.5Published30 Sep 2020
  3. 55%

    Directory traversal vulnerability in the Import/Export System Backups functionality in Apache OpenMeetings before 3.1.1 allows remote authenticated administrators to write to arbitrary files via a ..

    CVSS6.5Published11 Apr 2016
  4. 8.0%

    Cross-site scripting (XSS) vulnerability in Apache OpenMeetings before 3.1.1 allows remote attackers to inject arbitrary web script or HTML via the event description when creating an event.

    CVSS6.1Published11 Apr 2016
  5. 7.1%

    The sendHashByUser function in Apache OpenMeetings before 3.1.1 generates predictable password reset tokens, which makes it easier for remote attackers to reset arbitrary user passwords by leveraging knowledge of a...

    CVSS7.5Published11 Apr 2016
  6. 7.0%

    The (1) FileService.importFileByInternalUserId and (2) FileService.importFile SOAP API methods in Apache OpenMeetings before 3.1.1 improperly use the Java URL class without checking the specified protocol handler,...

    CVSS7.5Published11 Apr 2016
  7. 4.9%

    Cross-site scripting (XSS) vulnerability in the SWF panel in Apache OpenMeetings before 3.1.2 allows remote attackers to inject arbitrary web script or HTML via the swf parameter.

    CVSS6.1Published19 Aug 2016
  8. 4.8%

    Apache OpenMeetings before 3.1.2 is vulnerable to Remote Code Execution via RMI deserialization attack.

    CVSS9.8Published12 Oct 2017
  9. 3.0%

    Apache OpenMeetings 1.0.0 updates user password in insecure manner.

    CVSS7.5Published17 Jul 2017
  10. 2.9%

    Apache OpenMeetings 1.0.0 responds to the following insecure HTTP methods: PUT, DELETE, HEAD, and PATCH.

    CVSS5.3Published17 Jul 2017
EdgeProtect

Running Openmeetings? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 25 published vulnerabilities listed under the name Openmeetings, across 39 versions.

None of Openmeetings's vulnerabilities is on the list of flaws known to be exploited today.

Create a EdgeProtect account and track Openmeetings. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.