ghsa-xr9h-p2rc-rpqm
Vulnerability from github
Published
2023-05-01 22:30
Modified
2023-05-01 22:30
Severity ?
8.0 (High) - CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
Summary
WWBN/AVideo stored XSS vulnerability leads to takeover of any user's account, including admin's account
Details

In AVideo, a normal user can make a Meeting Schedule where the user can invite another user in that Meeting, but I found out that it did not properly sanitize the malicious characters when creating a Meeting Room. This leads the attacker to put malicious scripts.

Impact:

Since any USER including the ADMIN can see the meeting room that was created by the attacker this can lead to cookie hijacking and takeover of any accounts without user interaction.

Step to Reproduce:

  1. As normal USER go to Meet -> Schedule

https://demo.avideo.com/plugin/Meet/

  1. In "Meet topic" field put XSS payload

Example: ">

  1. Then click Save

  2. Now as ADMIN go to Meet -> Schedule -> Upcoming

https://demo.avideo.com/plugin/Meet/

  1. Then the XSS payload that normal USER created will be executed

Video POC: https://youtu.be/Nke0Bmv5F-o

Show details on source website

To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "Packagist",
        "name": "wwbn/avideo"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "12.4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2023-30860"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-79"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2023-05-01T22:30:28Z",
    "nvd_published_at": "2023-05-08T19:15:12Z",
    "severity": "HIGH"
  },
  "details": "In AVideo, a normal user can make a Meeting Schedule where the user can invite another user in that Meeting, but I found out that it did not properly sanitize the malicious characters when creating a Meeting Room. This leads the attacker to put malicious scripts.\n\nImpact:\n\nSince any USER including the ADMIN can see the meeting room that was created by the attacker this can lead to cookie hijacking and takeover of any accounts without user interaction.\n\nStep to Reproduce:\n\n1. As normal USER go to Meet -\u003e Schedule\n\nhttps://demo.avideo.com/plugin/Meet/\n\n2. In \"Meet topic\" field put XSS payload\n\nExample: \"\u003e\u003cimg src=x onerror=alert(\u0027Pawned+by+Gonz\u0027)\u003e\n\n3. Then click Save\n\n4. Now as ADMIN go to Meet -\u003e Schedule -\u003e Upcoming\n\nhttps://demo.avideo.com/plugin/Meet/\n\n5. Then the XSS payload that normal USER created will be executed\n\n\n\nVideo POC: https://youtu.be/Nke0Bmv5F-o",
  "id": "GHSA-xr9h-p2rc-rpqm",
  "modified": "2023-05-01T22:30:28Z",
  "published": "2023-05-01T22:30:28Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/WWBN/AVideo/security/advisories/GHSA-xr9h-p2rc-rpqm"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-30860"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/WWBN/AVideo"
    },
    {
      "type": "WEB",
      "url": "https://youtu.be/Nke0Bmv5F-o"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "WWBN/AVideo stored XSS vulnerability leads to takeover of any user\u0027s account, including admin\u0027s account"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.