dbcve.org
OpenmeetingsApplication · Apache

CVE-2017-7666

HIGH · 8.8 CVSS v3.0 Published 2017-07-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Apache OpenMeetings 1.0.0 is vulnerable to Cross-Site Request Forgery (CSRF) attacks, XSS attacks, click-jacking, and MIME based attacks.

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

Apache OpenMeetings 1.0.0 contains multiple web security vulnerabilities including Cross-Site Request Forgery (CSRF), Cross-Site Scripting (XSS), click-jacking, and MIME-based attacks. These are classic web application vulnerabilities that can allow attackers to perform actions on behalf of authenticated users, inject malicious scripts, hijack user clicks, or cause browsers to execute unintended content types.

MitigationUpgrade to a patched version of Apache OpenMeetings and implement standard web security controls including CSRF tokens, XSS sanitization, X-Frame-Options headers, and proper MIME type validation/handling.

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:= 1.0.0= 2.0= 2.1= 2.1.1= 2.2.0= 3.0.0= 3.0.1= 3.0.2= 3.0.3= 3.0.4= 3.0.5= 3.0.6

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 Apache OpenMeetings installation
    Check HTTP response headers for 'Server' or 'X-Powered-By' containing 'OpenMeetings', or access the application login page and look for OpenMeetings branding
    Affected if OpenMeetings is detected in the environment
  2. Determine installed version
    Access the application login page, about page, or check the Server HTTP header for version information. If available, also check the installation directory for version files or the administration panel
    Affected if The installed version matches one of the affected versions: 1.0.0, 2.0, 2.1, 2.1.1, 2.2.0, 3.0.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4, 3.0.5, or 3.0.6
  3. Check for X-Frame-Options header
    Inspect HTTP responses from the application using browser developer tools or a command-line tool like curl -I, and look for the X-Frame-Options or Content-Security-Policy header in the response headers
    Affected if The X-Frame-Options header is absent, indicating vulnerability to click-jacking attacks
  4. Verify CSRF protection
    Submit a form within the application and inspect whether a CSRF token or similar anti-CSRF mechanism is required for state-changing actions
    Affected if State-changing actions (such as creating rooms, uploading files, or modifying settings) do not require CSRF tokens or validation
  5. Check for XSS sanitization
    Attempt to inject a benign XSS payload (such as <script>alert(1)</script>) into input fields within the application and observe if the input is properly sanitized or encoded in the output
    Affected if User-supplied input is reflected back without sanitization or encoding, allowing script execution

The environment is affected if Apache OpenMeetings versions 1.0.0 through 3.0.6 are installed and the application lacks X-Frame-Options headers, CSRF tokens, or XSS input sanitization.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of Apache OpenMeetings and implement standard web security controls including CSRF tokens, XSS sanitization, X-Frame-Options headers, and proper MIME type validation/handling.

Fix this in Openmeetings Scoped from the published advisory
  • Consultation6.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA6.0 h
48.0 hours of engineering $8,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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