Security readout for executives and security teams
Plain-English summary
Scriban versions before 7.2.2 can let template code change host-application objects in ways developers intended to prohibit. Where attackers can supply or influence templates, they may alter sensitive state, including properties with private, internal, or init-only setters. Changes can persist after rendering, creating serious confidentiality, integrity, and availability risk.
Executive priority
Treat internet-facing or multi-tenant systems accepting untrusted templates as urgent. Prioritize upgrading and exposure review immediately because unauthorized state changes may persist in the host application. Systems without attacker-influenced templates should still confirm versions and object exposure, but their practical urgency may be lower.
Technical view
TypedObjectAccessor fails to enforce CLR setter visibility when assigning properties. Template code can consequently write private, internal, or init-only properties and mass-assign properties with public setters. The supplied CVSS 3.1 score is 9.8. Practical impact depends on whether an application exposes live CLR objects to attacker-influenced Scriban templates.
Likely exposure
Exposure is most likely in applications embedding Scriban before 7.2.2 that execute attacker-controlled or attacker-influenced templates against live CLR objects. Applications using only trusted templates, not exposing mutable host objects, or already running 7.2.2 or later have lower or no indicated exposure. The bundle does not identify specific downstream applications.
Exploitation context
The supplied record marks this vulnerability as not present in KEV, and no cited evidence in the bundle establishes active exploitation. The CVSS vector describes network-reachable, low-complexity, unauthenticated exploitation without user interaction, but actual reachability and privileges depend on each application's template ingestion and object-exposure design.
Researcher notes
Assessment should focus on the trust boundary between template authors and exposed CLR objects. Confirm the installed Scriban version, template provenance, object accessor configuration, and whether rendering receives live mutable instances. The bundle supports arbitrary property writes, but does not document public exploitation, affected downstream products, or application-specific impact paths.
Mitigation direction
- Upgrade Scriban to version 7.2.2 or later following vendor guidance.
- Restrict template creation and modification to trusted, authorized users.
- Avoid exposing sensitive or mutable live CLR objects to templates.
- Review vendor advisories for any additional hardening or compatibility guidance.
Validation and detection
- Inventory applications and dependencies to identify Scriban versions before 7.2.2.
- Identify whether untrusted users can create, upload, edit, or influence templates.
- Review template contexts for exposed live CLR objects and sensitive properties.
- After upgrading, verify templates cannot modify non-public or init-only setters.
- Test that rendering does not unexpectedly persist changes to host objects.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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 lookupCVE-2026-73061 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security Advisory (GHSA-7jvp-hj45-2f2m)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: Scriban before 7.2.2 Arbitrary Property Write via TypedObjectAccessorCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.