How severe is GHSA-32wx-4gxx-h48f?

No CVSS score has been assigned to GHSA-32wx-4gxx-h48f yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-32wx-4gxx-h48f?

GHSA-32wx-4gxx-h48f affects the following packages: flarum/tags (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-32wx-4gxx-h48f?

Update flarum/tags to 0.1.0-beta.13.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-32wx-4gxx-h48f is resolved across your whole dependency graph.

How do I detect GHSA-32wx-4gxx-h48f in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for flarum/tags, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-32wx-4gxx-h48f if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-32wx-4gxx-h48f actively exploited in the wild?

No public exploit code has been indexed for GHSA-32wx-4gxx-h48f yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-32wx-4gxx-h48f published, and has it been updated?

GHSA-32wx-4gxx-h48f was published on January 29, 2021 and was last updated on December 2, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

Users can edit the tags of any discussionGHSA-32wx-4gxx-h48f

Fix: flarum/tags@c8fcd00

GHSA-32wx-4gxx-h48f is a security vulnerability in flarum/tags. A fix is available for flarum/tags — see the affected versions and patch details below.

Published

Jan 29, 2021

Updated

Dec 2, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 2, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘flarum/tags

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

This advisory concerns a vulnerability which was patched and publicly released on October 5, 2020.

Impact

This vulnerability allowed any registered user to edit the tags of any discussion for which they have READ access using the REST API.

Users 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.

By 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.

The 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.

Forums 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.

Forums that don't use the Tags extension are unaffected.

Patches

The 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.

Workarounds

Version 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.

Forums that have not yet updated to Flarum beta 13 are encouraged to update as soon as possible.

References

For more information

If you have any questions or comments about this advisory, please start a new discussion on our support forum.

If you discover a security vulnerability within Flarum, please send an e-mail to [email protected]. All security vulnerabilities will be promptly addressed. More details can be found in our security policy.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`flarum/tags`	all versions	0.1.0-beta.13.2`composer require flarum/tags:^0.1.0-beta.13.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for flarum/tags, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update flarum/tags to 0.1.0-beta.13.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-32wx-4gxx-h48f is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

This advisory concerns a vulnerability which was patched and publicly released on October 5, 2020. ### Impact This vulnerability allowed any registered user to edit the tags of any discussion for which they have READ access using the REST API. Users 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. By 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

O3 Security · Impact-Aware SCA

Is GHSA-32wx-4gxx-h48f in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works