Permissions by Term - Moderately critical - Information disclosure - SA-CONTRIB-2026-214
Permissions by Term versions before 3.1.41 are affected when the module runs in Permission mode. The fix is to upgrade to 3.1.41. No vendor rating is given, so only the CVSS score of 3.7 (low) applies.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 3.1.41
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Improper Check for Unusual or Exceptional Conditions vulnerability in Drupal Permissions by Term allows Forceful Browsing. This issue affects Permissions by Term versions: from 0.0.0 to 3.1.41.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Drupal Permissions by Term
From 0.0.0 · fixed in 3.1.41
References 1
drupal.org
Questions about CVE-2026-107311
What does this mean?
Nodes that should be restricted can be read through JSON:API when they reference a deleted taxonomy term. This is an information disclosure flaw.Source: drupal.org
Am I affected, and how do I check?
Permissions by Term versions before 3.1.41 are affected, and only when the module is in Permission mode and nodes are accessed via JSON:API. Check the installed Permissions by Term version and the module's mode setting to see whether these conditions apply.Source: drupal.org
What should I do about it?
Upgrade to Permissions by Term 3.1.41.Source: drupal.org
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data