LiveActive security incident?Get immediate response
CVE Record

CVE-2021-46372: Scoold 1.47.2 is a Q&A/knowledge base platform written in Java.

Scoold 1.47.2 is a Q&A/knowledge base platform written in Java. When writing a Q&A, the markdown editor is vulnerable to a XSS attack when using uppercase letters.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2021-46372 describes a cross-site scripting issue in Scoold 1.47.2, a Java Q&A/knowledge base platform. The reported weakness is in the markdown editor when uppercase letters are used. The source bundle does not provide CVSS scoring, a confirmed patch, or evidence of active exploitation.

Executive priority

Treat this as a targeted hygiene item, not an emergency based on current evidence. Prioritize if Scoold 1.47.2 is internet-facing or accepts content from many users.

Technical view

The CVE states that Scoold 1.47.2's Q&A markdown editor is vulnerable to XSS involving uppercase letters. Available evidence is sparse: affected CPEs, CWE, CVSS, exploit maturity, and remediation details are not supplied in the provided sources.

Likely exposure

Exposure is likely limited to deployments running Scoold 1.47.2 where users can create or edit Q&A content through the markdown editor. Risk depends on who can post content and who views it.

Exploitation context

The CVE is not listed as KEV in the bundle, and no cited source states active exploitation. The public description indicates an XSS condition, but does not provide operational exploitation details or impact scope.

Researcher notes

The public record lacks CVSS, CWE, CPE, and remediation metadata. Validate exposure through asset inventory and role permissions rather than assuming broad impact. Avoid relying on inferred fixes without maintainer confirmation.

Mitigation direction

  • Identify whether Scoold 1.47.2 is deployed.
  • Check Scoold maintainer or vendor guidance for fixed versions.
  • Restrict Q&A authoring to trusted users until remediated.
  • Moderate or remove suspicious markdown content.
  • Use browser-side protections such as CSP where supported.

Validation and detection

  • Inventory Scoold instances and confirm exact version.
  • Review who can create or edit Q&A posts.
  • Check existing Q&A content for unexpected script-like markup.
  • Monitor vendor advisories for patch or workaround confirmation.
  • Record that active exploitation is not evidenced by supplied sources.
Prepared
Confidence
medium
Sources
3

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.

cve · low confidence lookup

CVE-2021-46372 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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