{
  "GSD": {
    "alias": "CVE-2023-22489",
    "id": "GSD-2023-22489"
  },
  "gsd": {
    "metadata": {
      "exploitCode": "unknown",
      "remediation": "unknown",
      "reportConfidence": "confirmed",
      "type": "vulnerability"
    },
    "osvSchema": {
      "aliases": [
        "CVE-2023-22489"
      ],
      "details": "Flarum is a discussion platform for websites. If the first post of a discussion is permanently deleted but the discussion stays visible, any actor who can view the discussion is able to create a new reply via the REST API, no matter the reply permission or lock status. This includes users that don\u0027t have a validated email. Guests cannot successfully create a reply because the API will fail with a 500 error when the user ID 0 is inserted into the database. This happens because when the first post of a discussion is permanently deleted, the `first_post_id` attribute of the discussion becomes `null` which causes access control to be skipped for all new replies. Flarum automatically makes discussions with zero comments invisible so an additional condition for this vulnerability is that the discussion must have at least one approved reply so that `discussions.comment_count` is still above zero after the post deletion. This can open the discussion to uncontrolled spam or just unintentional replies if users still had their tab open before the vulnerable discussion was locked and then post a reply when they shouldn\u0027t be able to. In combination with the email notification settings, this could also be used as a way to send unsolicited emails. Versions between `v1.3.0` and `v1.6.3` are impacted. The vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum should upgrade as soon as possible. There are no known workarounds.",
      "id": "GSD-2023-22489",
      "modified": "2023-12-13T01:20:43.349154Z",
      "schema_version": "1.4.0"
    }
  },
  "namespaces": {
    "cve.org": {
      "CVE_data_meta": {
        "ASSIGNER": "security-advisories@github.com",
        "ID": "CVE-2023-22489",
        "STATE": "PUBLIC"
      },
      "affects": {
        "vendor": {
          "vendor_data": [
            {
              "product": {
                "product_data": [
                  {
                    "product_name": "framework",
                    "version": {
                      "version_data": [
                        {
                          "version_affected": "=",
                          "version_value": "\u003e= 1.3.0, \u003c 1.6.3"
                        }
                      ]
                    }
                  }
                ]
              },
              "vendor_name": "flarum"
            }
          ]
        }
      },
      "data_format": "MITRE",
      "data_type": "CVE",
      "data_version": "4.0",
      "description": {
        "description_data": [
          {
            "lang": "eng",
            "value": "Flarum is a discussion platform for websites. If the first post of a discussion is permanently deleted but the discussion stays visible, any actor who can view the discussion is able to create a new reply via the REST API, no matter the reply permission or lock status. This includes users that don\u0027t have a validated email. Guests cannot successfully create a reply because the API will fail with a 500 error when the user ID 0 is inserted into the database. This happens because when the first post of a discussion is permanently deleted, the `first_post_id` attribute of the discussion becomes `null` which causes access control to be skipped for all new replies. Flarum automatically makes discussions with zero comments invisible so an additional condition for this vulnerability is that the discussion must have at least one approved reply so that `discussions.comment_count` is still above zero after the post deletion. This can open the discussion to uncontrolled spam or just unintentional replies if users still had their tab open before the vulnerable discussion was locked and then post a reply when they shouldn\u0027t be able to. In combination with the email notification settings, this could also be used as a way to send unsolicited emails. Versions between `v1.3.0` and `v1.6.3` are impacted. The vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum should upgrade as soon as possible. There are no known workarounds."
          }
        ]
      },
      "impact": {
        "cvss": [
          {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 3.5,
            "baseSeverity": "LOW",
            "confidentialityImpact": "NONE",
            "integrityImpact": "LOW",
            "privilegesRequired": "LOW",
            "scope": "UNCHANGED",
            "userInteraction": "REQUIRED",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N",
            "version": "3.1"
          }
        ]
      },
      "problemtype": {
        "problemtype_data": [
          {
            "description": [
              {
                "cweId": "CWE-862",
                "lang": "eng",
                "value": "CWE-862: Missing Authorization"
              }
            ]
          }
        ]
      },
      "references": {
        "reference_data": [
          {
            "name": "https://github.com/flarum/framework/security/advisories/GHSA-hph3-hv3c-7725",
            "refsource": "MISC",
            "url": "https://github.com/flarum/framework/security/advisories/GHSA-hph3-hv3c-7725"
          },
          {
            "name": "https://github.com/flarum/framework/commit/12f14112a0ecd1484d97330b82beb2a145919015",
            "refsource": "MISC",
            "url": "https://github.com/flarum/framework/commit/12f14112a0ecd1484d97330b82beb2a145919015"
          },
          {
            "name": "https://github.com/flarum/framework/releases/tag/v1.6.3",
            "refsource": "MISC",
            "url": "https://github.com/flarum/framework/releases/tag/v1.6.3"
          }
        ]
      },
      "source": {
        "advisory": "GHSA-hph3-hv3c-7725",
        "discovery": "UNKNOWN"
      }
    },
    "gitlab.com": {
      "advisories": [
        {
          "affected_range": "\u003e=1.3.0,\u003c1.6.2",
          "affected_versions": "All versions starting from 1.3.0 before 1.6.2",
          "cvss_v3": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N",
          "cwe_ids": [
            "CWE-1035",
            "CWE-862",
            "CWE-937"
          ],
          "date": "2023-01-23",
          "description": "Flarum is a discussion platform for websites. If the first post of a discussion is permanently deleted but the discussion stays visible, any actor who can view the discussion is able to create a new reply via the REST API, no matter the reply permission or lock status. This includes users that don\u0027t have a validated email. Guests cannot successfully create a reply because the API will fail with a 500 error when the user ID 0 is inserted into the database. This happens because when the first post of a discussion is permanently deleted, the `first_post_id` attribute of the discussion becomes `null` which causes access control to be skipped for all new replies. Flarum automatically makes discussions with zero comments invisible so an additional condition for this vulnerability is that the discussion must have at least one approved reply so that `discussions.comment_count` is still above zero after the post deletion. This can open the discussion to uncontrolled spam or just unintentional replies if users still had their tab open before the vulnerable discussion was locked and then post a reply when they shouldn\u0027t be able to. In combination with the email notification settings, this could also be used as a way to send unsolicited emails. Versions between `v1.3.0` and `v1.6.3` are impacted. The vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum should upgrade as soon as possible. There are no known workarounds.",
          "fixed_versions": [
            "1.6.2"
          ],
          "identifier": "CVE-2023-22489",
          "identifiers": [
            "CVE-2023-22489",
            "GHSA-hph3-hv3c-7725",
            "GMS-2023-11"
          ],
          "not_impacted": "All versions before 1.3.0, all versions starting from 1.6.2",
          "package_slug": "packagist/flarum/core",
          "pubdate": "2023-01-13",
          "solution": "Upgrade to version 1.6.2 or above.",
          "title": "Missing Authorization",
          "urls": [
            "https://nvd.nist.gov/vuln/detail/CVE-2023-22489",
            "https://github.com/flarum/framework/commit/12f14112a0ecd1484d97330b82beb2a145919015",
            "https://github.com/flarum/framework/security/advisories/GHSA-hph3-hv3c-7725",
            "https://github.com/flarum/framework/releases/tag/v1.6.3",
            "https://github.com/advisories/GHSA-hph3-hv3c-7725"
          ],
          "uuid": "e5032f22-9e51-4b95-9a90-4d7401568864"
        },
        {
          "affected_range": "\u003c0",
          "affected_versions": "All versions starting from 1.3.0 before 1.6.3",
          "cwe_ids": [
            "CWE-1035",
            "CWE-937"
          ],
          "date": "2023-01-10",
          "description": "If the first post of a discussion is permanently deleted but the discussion stays visible, any actor who can view the discussion is able to create a new reply via the REST API, no matter the reply permission or lock status.\n\nThis includes users that don\u0027t have a validated email.\n\nGuests cannot successfully create a reply because the API will fail with a 500 error when the user ID 0 is inserted into the database. This should also be fixed to return the expected 401/403 status.\n\nThis happens because when the first post of a discussion is permanently deleted, the `first_post_id` attribute of the discussion becomes `null` which causes access control to be skipped for all new replies.\n\nFlarum automatically makes discussions with zero comments invisible so an additional condition for this vulnerability is that the discussion must have at least one approved reply so that `discussions.comment_count` is still above zero after the post deletion.\n\n### Impact\nThis can open the discussion to uncontrolled spam or just unintentional replies if users still had their tab open before the vulnerable discussion was locked and then post a reply when they shouldn\u0027t be able to.\n\nIn combination with the email notification settings, this could also be used as a way to send unsolicited emails.\n\nVersions between `v1.3.0` and `v1.6.3` are impacted.\n\n### Patches\nThe vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum should upgrade as soon as possible to v1.6.3 using:\n\n```\ncomposer update --prefer-dist --no-dev -a -W\n```\nYou can then confirm you run the latest version using:\n\n```\ncomposer show flarum/core\n```\n\n### Workarounds\nIf you don\u0027t delete the first posts you are not affected. A workaround can be to delete the discussion itself, or amend the database to manually set a `first_post_id`.\n\n### For more information\nFor any questions or comments on this vulnerability please visit https://discuss.flarum.org/\n\nFor support questions create a discussion at https://discuss.flarum.org/t/support.\n\nA reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing [security@flarum.org](mailto:security@flarum.org), and we will address it promptly.\n",
          "fixed_versions": [
            "1.6.3"
          ],
          "identifier": "GMS-2023-11",
          "identifiers": [
            "GHSA-hph3-hv3c-7725",
            "GMS-2023-11",
            "CVE-2023-22489"
          ],
          "not_impacted": "All versions before 1.3.0, all versions starting from 1.6.3",
          "package_slug": "packagist/flarum/core",
          "pubdate": "2023-01-10",
          "solution": "Upgrade to version 1.6.3 or above.",
          "title": "Duplicate of ./packagist/flarum/core/CVE-2023-22489.yml",
          "urls": [
            "https://github.com/flarum/framework/security/advisories/GHSA-hph3-hv3c-7725",
            "https://github.com/flarum/framework/commit/12f14112a0ecd1484d97330b82beb2a145919015",
            "https://github.com/flarum/framework/releases/tag/v1.6.3",
            "https://github.com/advisories/GHSA-hph3-hv3c-7725"
          ],
          "uuid": "f52ee4d1-616f-472b-ba5c-aee89c68ece4"
        },
        {
          "affected_range": "\u003e=1.3.0,\u003c1.6.2",
          "affected_versions": "All versions starting from 1.3.0 before 1.6.2",
          "cvss_v3": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N",
          "cwe_ids": [
            "CWE-1035",
            "CWE-862",
            "CWE-937"
          ],
          "date": "2023-01-23",
          "description": "Flarum is a discussion platform for websites. If the first post of a discussion is permanently deleted but the discussion stays visible, any actor who can view the discussion is able to create a new reply via the REST API, no matter the reply permission or lock status. This includes users that don\u0027t have a validated email. Guests cannot successfully create a reply because the API will fail with a 500 error when the user ID 0 is inserted into the database. This happens because when the first post of a discussion is permanently deleted, the `first_post_id` attribute of the discussion becomes `null` which causes access control to be skipped for all new replies. Flarum automatically makes discussions with zero comments invisible so an additional condition for this vulnerability is that the discussion must have at least one approved reply so that `discussions.comment_count` is still above zero after the post deletion. This can open the discussion to uncontrolled spam or just unintentional replies if users still had their tab open before the vulnerable discussion was locked and then post a reply when they shouldn\u0027t be able to. In combination with the email notification settings, this could also be used as a way to send unsolicited emails. Versions between `v1.3.0` and `v1.6.3` are impacted. The vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum should upgrade as soon as possible. There are no known workarounds.",
          "fixed_versions": [],
          "identifier": "CVE-2023-22489",
          "identifiers": [
            "CVE-2023-22489",
            "GHSA-hph3-hv3c-7725"
          ],
          "not_impacted": "",
          "package_slug": "packagist/flarum/flarum",
          "pubdate": "2023-01-13",
          "solution": "Unfortunately, there is no solution available yet.",
          "title": "Missing Authorization",
          "urls": [
            "https://nvd.nist.gov/vuln/detail/CVE-2023-22489",
            "https://github.com/flarum/framework/commit/12f14112a0ecd1484d97330b82beb2a145919015",
            "https://github.com/flarum/framework/security/advisories/GHSA-hph3-hv3c-7725",
            "https://github.com/flarum/framework/releases/tag/v1.6.3"
          ],
          "uuid": "1c487617-f1b1-4d3b-b2aa-221cd24b5610"
        }
      ]
    },
    "nvd.nist.gov": {
      "configurations": {
        "CVE_data_version": "4.0",
        "nodes": [
          {
            "children": [],
            "cpe_match": [
              {
                "cpe23Uri": "cpe:2.3:a:flarum:flarum:*:*:*:*:*:*:*:*",
                "cpe_name": [],
                "versionEndExcluding": "1.6.2",
                "versionStartIncluding": "1.3.0",
                "vulnerable": true
              }
            ],
            "operator": "OR"
          }
        ]
      },
      "cve": {
        "CVE_data_meta": {
          "ASSIGNER": "security-advisories@github.com",
          "ID": "CVE-2023-22489"
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "en",
              "value": "Flarum is a discussion platform for websites. If the first post of a discussion is permanently deleted but the discussion stays visible, any actor who can view the discussion is able to create a new reply via the REST API, no matter the reply permission or lock status. This includes users that don\u0027t have a validated email. Guests cannot successfully create a reply because the API will fail with a 500 error when the user ID 0 is inserted into the database. This happens because when the first post of a discussion is permanently deleted, the `first_post_id` attribute of the discussion becomes `null` which causes access control to be skipped for all new replies. Flarum automatically makes discussions with zero comments invisible so an additional condition for this vulnerability is that the discussion must have at least one approved reply so that `discussions.comment_count` is still above zero after the post deletion. This can open the discussion to uncontrolled spam or just unintentional replies if users still had their tab open before the vulnerable discussion was locked and then post a reply when they shouldn\u0027t be able to. In combination with the email notification settings, this could also be used as a way to send unsolicited emails. Versions between `v1.3.0` and `v1.6.3` are impacted. The vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum should upgrade as soon as possible. There are no known workarounds."
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "en",
                  "value": "CWE-862"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://github.com/flarum/framework/commit/12f14112a0ecd1484d97330b82beb2a145919015",
              "refsource": "MISC",
              "tags": [
                "Patch",
                "Third Party Advisory"
              ],
              "url": "https://github.com/flarum/framework/commit/12f14112a0ecd1484d97330b82beb2a145919015"
            },
            {
              "name": "https://github.com/flarum/framework/security/advisories/GHSA-hph3-hv3c-7725",
              "refsource": "MISC",
              "tags": [
                "Mitigation",
                "Third Party Advisory"
              ],
              "url": "https://github.com/flarum/framework/security/advisories/GHSA-hph3-hv3c-7725"
            },
            {
              "name": "https://github.com/flarum/framework/releases/tag/v1.6.3",
              "refsource": "MISC",
              "tags": [
                "Release Notes",
                "Third Party Advisory"
              ],
              "url": "https://github.com/flarum/framework/releases/tag/v1.6.3"
            }
          ]
        }
      },
      "impact": {
        "baseMetricV3": {
          "cvssV3": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 3.5,
            "baseSeverity": "LOW",
            "confidentialityImpact": "NONE",
            "integrityImpact": "LOW",
            "privilegesRequired": "LOW",
            "scope": "UNCHANGED",
            "userInteraction": "REQUIRED",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N",
            "version": "3.1"
          },
          "exploitabilityScore": 2.1,
          "impactScore": 1.4
        }
      },
      "lastModifiedDate": "2023-01-23T17:55Z",
      "publishedDate": "2023-01-13T19:15Z"
    }
  }
}