LiveActive security incident?Get immediate response
CVE Record

CVE-2021-4267: tad_discuss cross site scripting

A vulnerability classified as problematic was found in tad_discuss. Affected by this vulnerability is an unknown functionality. The manipulation of the argument DiscussTitle leads to cross site scripting. The attack can be launched remotely. The name of the patch is af94d034ff8db642d05fd8788179eab05f433958. It is recommended to apply a patch to fix this issue. The identifier VDB-216469 was assigned to this vulnerability.

LowCVSS 3.5Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2021-4267 is a low-severity cross-site scripting issue in tad_discuss involving the DiscussTitle argument. A remote attacker with some privileges could affect page integrity if a user interaction condition is met. The public sources name a patch, but do not identify affected versions or detailed product packaging.

Executive priority

Handle through normal patch management unless tad_discuss is externally exposed or accepts content from many low-trust users. Business risk is mainly page integrity and user trust, not direct system compromise, based on the provided CVSS and sources.

Technical view

The CVE describes XSS through manipulation of DiscussTitle in tad_discuss, mapped to CWE-707. CVSS 3.1 is 3.5 with network attack vector, low complexity, low privileges, required user interaction, unchanged scope, no confidentiality or availability impact, and low integrity impact. The patched commit is af94d034ff8db642d05fd8788179eab05f433958.

Likely exposure

Exposure is likely limited to organizations running tad_discuss where low-privileged users can submit or influence DiscussTitle content. The sources do not provide affected version ranges, CPEs, hosting details, or deployment prevalence, so inventory confirmation is required.

Exploitation context

The issue is remotely reachable according to the CVE description, but it requires privileges and user interaction per CVSS. The source bundle does not show CISA KEV listing or active exploitation evidence. Treat exploitation status as unconfirmed, not known exploited.

Researcher notes

Key evidence gaps are affected versions, exact vulnerable functionality, and exploit observations. The CVE and VulDB record classify this as XSS via DiscussTitle, with the GitHub PR and commit serving as the concrete remediation reference.

Mitigation direction

  • Update tad_discuss to a revision containing commit af94d034ff8db642d05fd8788179eab05f433958.
  • Review the upstream pull request and commit for vendor-intended remediation details.
  • Prioritize public or semi-public deployments where untrusted users can set DiscussTitle.
  • Check vendor or project guidance for any later release notes or backport instructions.

Validation and detection

  • Inventory applications and sites using tad_discuss.
  • Confirm deployed code includes the patched commit or a later trusted release.
  • Review whether DiscussTitle can be influenced by low-privileged users.
  • Verify DiscussTitle output is safely handled using approved non-destructive security test cases.
  • Record any unknown version mappings as residual risk until vendor guidance is confirmed.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-707: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-4267 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
3.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
3.5CVSS 3.1LowCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N2.11.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

3.5Low
CVSS 3.1 vector shape for CVE-2021-4267Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
unspecifiedtad_discussn/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-707 · source CWE mapping

Improper Neutralization

Improper Neutralization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.