ghsa-p3m2-mj3j-j49x
Vulnerability from github
Published
2024-10-24 17:45
Modified
2024-10-28 19:40
Severity ?
7.1 (High) - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N
5.2 (Medium) - CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:P/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N
Summary
baserCMS has a Cross-site Scripting (XSS) Vulnerability in Edit Email Form Settings Feature
Details

XSS vulnerability in Edit Email Form Settings Feature to baserCMS.

Target

baserCMS 5.1.1 and earlier versions

Vulnerability

Malicious code may be executed in Edit Email Form Settings feature.

Countermeasures

Update to the latest version of baserCMS

Please refer to the following page to reference for more information. https://basercms.net/security/JVN_00876083

Credits

Ayato Shitomi＠Fore-Z

Show details on source website

To clipboard 

{
   affected: [
      {
         database_specific: {
            last_known_affected_version_range: "<= 5.1.1",
         },
         package: {
            ecosystem: "Packagist",
            name: "baserproject/basercms",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "0",
                  },
                  {
                     fixed: "5.1.2",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
   ],
   aliases: [
      "CVE-2024-46998",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-79",
      ],
      github_reviewed: true,
      github_reviewed_at: "2024-10-24T17:45:58Z",
      nvd_published_at: "2024-10-24T19:15:14Z",
      severity: "MODERATE",
   },
   details: "XSS vulnerability in Edit Email Form Settings Feature to baserCMS.\n\n### Target\nbaserCMS 5.1.1 and earlier versions\n\n### Vulnerability\nMalicious code may be executed in Edit Email Form Settings feature.\n\n### Countermeasures\nUpdate to the latest version of baserCMS\n\nPlease refer to the following page to reference for more information.\nhttps://basercms.net/security/JVN_00876083\n\n### Credits\nAyato Shitomi＠Fore-Z\n",
   id: "GHSA-p3m2-mj3j-j49x",
   modified: "2024-10-28T19:40:58Z",
   published: "2024-10-24T17:45:58Z",
   references: [
      {
         type: "WEB",
         url: "https://github.com/baserproject/basercms/security/advisories/GHSA-p3m2-mj3j-j49x",
      },
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2024-46998",
      },
      {
         type: "WEB",
         url: "https://basercms.net/security/JVN_00876083",
      },
      {
         type: "WEB",
         url: "https://basercms.net/security/JVN_98693329",
      },
      {
         type: "PACKAGE",
         url: "https://github.com/baserproject/basercms",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N",
         type: "CVSS_V3",
      },
      {
         score: "CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:P/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N",
         type: "CVSS_V4",
      },
   ],
   summary: "baserCMS has a Cross-site Scripting (XSS) Vulnerability in Edit Email Form Settings Feature",
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



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.