LiveActive security incident?Get immediate response
CVE Record

CVE-2021-4256: ctrlo lenio index.tt cross site scripting

A vulnerability was found in ctrlo lenio. It has been classified as problematic. This affects an unknown part of the file views/index.tt. The manipulation of the argument task.name/task.site.org.name leads to cross site scripting. It is possible to initiate the attack remotely. The name of the patch is e1646d5cd0a2fbab9eb505196dd2ca1c9e4cdd97. It is recommended to apply a patch to fix this issue. The identifier VDB-216213 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-4256 is a low-severity cross-site scripting issue in ctrlo Lenio. A user-controlled task or organization name could be rendered unsafely in the index template, allowing limited page-content manipulation when a victim interacts with the affected page.

Executive priority

Handle in normal patch cycles unless Lenio is internet-facing or widely used by untrusted users. Business impact appears limited to integrity of displayed content, not data theft or service outage, based on the provided CVSS metrics.

Technical view

The CVE describes XSS in ctrlo Lenio's views/index.tt through task.name or task.site.org.name. The CVSS 3.1 score is 3.5 with network attack vector, low complexity, required low privileges, and required user interaction. The cited fix is commit e1646d5cd0a2fbab9eb505196dd2ca1c9e4cdd97.

Likely exposure

Exposure is limited to organizations running ctrlo Lenio or forks that include the vulnerable views/index.tt behavior. The source bundle does not identify affected version ranges, fixed releases, or package names, so exposure requires repository or deployment-level verification.

Exploitation context

The record says remote attack is possible, but requires low privileges and user interaction. There is no KEV listing and no cited evidence of active exploitation in the provided sources.

Researcher notes

The public record is sparse: affected versions are listed as n/a, and the vulnerable code area is described only as views/index.tt. Analysis should focus on whether the fixing commit is present and whether equivalent downstream template changes exist.

Mitigation direction

  • Apply upstream patch commit e1646d5cd0a2fbab9eb505196dd2ca1c9e4cdd97 to affected Lenio deployments.
  • Check ctrlo/lenio vendor guidance for any tagged release containing the fix.
  • Review forks or local template customizations for equivalent unsafe rendering.
  • Prioritize externally reachable or multi-user Lenio instances.

Validation and detection

  • Inventory Lenio deployments and forks across production and internal environments.
  • Verify the patch commit or equivalent template escaping is present.
  • Review views/index.tt handling of task.name and task.site.org.name.
  • Confirm no vulnerable unpatched instances remain because version data is incomplete.
Prepared
Confidence
medium
Sources
4

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-4256 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
3Source 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-4256Attack 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
ctrlolenion/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.