Security readout for executives and security teams
Plain-English summary
Authenticated Lutece administrators may be able to turn a malicious XSL export template into arbitrary server-side code execution. A compromised or malicious administrator could potentially take over the application server and affect connected systems or data. The supplied record identifies Lutece Core through 7.1.7, but its structured version metadata is inconsistent.
Executive priority
Treat as an urgent privileged-access risk. Prioritize internet-facing or business-critical Lutece deployments and environments with weak administrator controls. Immediate inventory and access restriction are warranted, while the remediation owner confirms an official vendor fix. Escalate promptly if suspicious administrator or export activity is found.
Technical view
The export module processes administrator-supplied XSL stylesheets without enabling FEATURE_SECURE_PROCESSING. This permits Java extension functions during XSLT transformation, creating a CWE-94 code-injection path. Exploitation requires authenticated administrator privileges and triggering a user export operation; no user interaction is required.
Likely exposure
Potentially exposed deployments are Lutece Core installations using the XSL export management functionality through version 7.1.7. Exposure depends on an attacker obtaining administrator access. Confirm versions carefully because the structured affected-version field lists “0” while the narrative states “up to version 7.1.7.”
Exploitation context
The supplied sources do not report active exploitation, and CVE-2026-4813 is not identified as KEV in the bundle. The attack is network-accessible but requires high privileges. Its impact remains severe because successful exploitation could compromise the server and downstream confidentiality, integrity, and availability.
Researcher notes
The mechanism is specifically insecure XSLT processing that permits Java extension functions. The supplied record provides no vendor advisory, patch version, proof of concept, or exploitation evidence. Version data is internally inconsistent, so affected-range conclusions should remain provisional until authoritative vendor guidance is available.
Mitigation direction
- Inventory Lutece Core deployments and identify installations through version 7.1.7.
- Check current Lutece vendor guidance for an approved patch or upgrade target.
- Restrict administrator access to trusted personnel and protected management networks.
- Temporarily limit XSL upload and export functionality where operationally acceptable.
- Investigate suspected administrator-account compromise before restoring export operations.
Validation and detection
- Confirm each deployed Lutece Core version using authoritative installation records.
- Determine whether the XSL export management functionality is enabled and accessible.
- Review administrator activity for unexpected stylesheet uploads or export executions.
- Inspect server telemetry for anomalous child processes or application-account activity.
- Verify remediation against current vendor guidance without executing untrusted stylesheets.
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-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-4813 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.4 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA: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
1 official scoreWe 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:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H——INCIBEVulnerability scoring details
Base CVSS 4.0 score
9.4CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA: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
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 Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.