{"answers":{"affected":"2 open source packages ship an affected version, including flarum/tags.","exploited":"There is no known exploitation of GHSA-32wx-4gxx-h48f in the wild and no public exploit code.","fix":"Upgrade flarum/tags to 0.1.0-beta.13.2 or later.","what":"GHSA-32wx-4gxx-h48f is a missing authorization vulnerability in flarum/tags, published on 29 Jan 2021. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-32wx-4gxx-h48f and fix it if it is affected.\n\nWhat it is: GHSA-32wx-4gxx-h48f is a missing authorization vulnerability in flarum/tags, published on 29 Jan 2021. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-32wx-4gxx-h48f in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- flarum/tags (Packagist): affected all versions; fixed in 0.1.0-beta.13.2\n- flarum/tags (Packagist): affected all versions; fixed in 0.1.0-beta.13.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-32wx-4gxx-h48f/ (Markdown: https://insights.sbomify.com/GHSA-32wx-4gxx-h48f/index.md)","id":"GHSA-32wx-4gxx-h48f","markdown":"https://insights.sbomify.com/GHSA-32wx-4gxx-h48f/index.md","name":"GHSA-32wx-4gxx-h48f","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Flarum Tags extension","requires_auth":"low_privilege","summary":"Registered users can bypass tag-based access controls to view or interact with restricted content by editing discussion tags via the API.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"This advisory concerns a vulnerability which was patched and publicly released on October 5, 2020.\n\n### Impact\nThis vulnerability allowed any registered user to edit the tags of any discussion for which they have READ access using the REST API.\n\nUsers were able to remove any existing tag, and add any tag in which they are allowed to create discussions. The chosen tags still had to match the configured Tags minimums and maximums.\n\nBy moving the discussion to new tags, users were able to go around permissions applied to restricted tags. Depending on the setup, this can include publicly exposing content that was only visible to certain groups, or gain the ability to interact with content where such interaction was limited.\n\nThe full impact varies depending on the configuration of permissions and restricted tags, and which community extensions are being used. All tag-scoped permissions offered by extensions are impacted by this ability to go around them.\n\nForums that don't use restricted tags and don't use any extension that relies on tags for access control should not see any security impact. An update is still required to stop users from being able to change any discussion's tags.\n\nForums that don't use the Tags extension are unaffected.\n\n### Patches\nThe fix will be available in version v0.1.0-beta.14 with Flarum beta 14. The fix has already been back-ported to Flarum beta 13 as version v0.1.0-beta.13.2 of the Tags extension.\n\n### Workarounds\nVersion v0.1.0-beta.13.2 of the Tags extension allows existing Flarum beta 13 forums to fix the issue without the need to update to beta 14.\n\nForums that have not yet updated to Flarum beta 13 are encouraged to update as soon as possible.\n\n### References\n\n- [Release announcement](https://discuss.flarum.org/d/25059-security-update-to-flarum-tags-010-beta132)\n- [GitHub issue](https://github.com/flarum/core/issues/2355)\n\n### For more information\nIf you have any questions or comments about this advisory, please start a new discussion on our [support forum](https://discuss.flarum.org/t/support).\n\nIf you discover a security vulnerability within Flarum, please send an e-mail to [security@flarum.org](mailto:security@flarum.org). All security vulnerabilities will be promptly addressed. More details can be found in our [security policy](https://github.com/flarum/core/security/policy).","ecosystems":["Packagist"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Users can edit the tags of any discussion","id":"GHSA-32wx-4gxx-h48f","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"missing_authorization","year":"2021"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["0.1.0-beta.13.2"],"introduced":["0"],"last_affected":[],"package":"flarum/tags","purl":null,"source":"GHSA-32wx-4gxx-h48f"},{"ecosystem":"Packagist","fixed":["0.1.0-beta.13.2"],"introduced":["0"],"last_affected":[],"package":"flarum/tags","purl":"pkg:composer/flarum/tags","source":"GHSA-32wx-4gxx-h48f"}],"products":null,"published":"2021-01-29","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Registered users can bypass tag-based access controls to view or interact with restricted content by editing discussion tags via the API.","url":"https://insights.sbomify.com/GHSA-32wx-4gxx-h48f/"}