VulnerabilityPublished 23 Mar 2026

CVE-2026-27131: putyourlightson craft-sprig · Information Exposure

Affects putyourlightson craft-sprigSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.5 Medium : upgrade to 3.15.2 or 2.15.2 when convenient.

Data as of 9 Nov 2026, 23:24 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.15.2, 2.15.2

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade putyourlightson craft-sprig to 3.15.2 or 2.15.2.

Affected software

Product	Affected	Fixed in
putyourlightsoncraft-sprig	Affected >=3.0.0 <3.15.2	Fixed in 3.15.2
putyourlightsoncraft-sprig	Affected >=2.0.0 <2.15.2	Fixed in 2.15.2
GitHubputyourlightson/craft-sprig`pkg:github/putyourlightson/craft-sprig`Other threats	Affected 2.0.0 – 3.15.2 4 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should upgrade the Sprig plugin to version 2.15.2 or 3.15.2 or later, where the vulnerability is fixed by disabling the Sprig Playground when devMode is off by default. If upgrading immediately is not feasible, ensure that the Craft CMS devMode is disabled in all production environments to prevent access to the Sprig Playground. Additionally, verify that the enablePlaygroundWhenDevModeDisabled setting is set to false to avoid accidental re-enabling of the playground. Review user permissions carefully to restrict Sprig Playground access only to trusted administrators. Conduct audits of configuration files and logs to detect any unauthorized access or data exposure. Remove or disable any leftover debug or development features in production deployments. Implement monitoring to detect unusual access patterns to the Sprig Playground or related components. Finally, consider rotating any potentially exposed keys or credentials as a precautionary measure.

Description

CVE-2026-27131 is a medium severity vulnerability in the Sprig plugin for Craft CMS that allows authorized admin users or users with explicit Sprig Playground access to expose sensitive information such as security keys and credentials. This exposure occurs in versions 2.0.0 up to but not including 2.15.2, and 3.0.0 up to but not including 3.15.2.

Impact

The primary impact of this vulnerability is the unauthorized exposure of sensitive information such as security keys and credentials to users who have administrative or explicit Sprig Playground permissions. Although exploitation requires authenticated access with elevated privileges, the leakage of sensitive configuration data can facilitate further attacks, including privilege escalation, unauthorized access to backend systems, or compromise of cryptographic operations relying on the exposed keys. Organizations running affected versions in production environments with devMode enabled or with the Sprig Playground enabled risk unintended data exposure. This can lead to loss of confidentiality, potential data breaches, and erosion of trust. Since Craft CMS is widely used for content management, especially in web applications, the vulnerability could affect a broad range of organizations, including enterprises, government agencies, and service providers. The absence of known exploits reduces immediate risk, but the presence of leftover debug functionality in production environments is a significant security concern that must be addressed promptly.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-489Active Debug Code (opens in a new tab)
Base weaknessOWASP Top 10 A02:2025: Security Misconfiguration (opens in a new tab)
The product is released with debugging code still enabled or active.
Build and Compilation · Distribution
Remove debug code before deploying the application.
Attack patterns
Exploit Non-Production Interfaces (opens in a new tab)
Root/Jailbreak Detection Evasion via Debugging (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Mar 2026, 20:40 UTC

WeaknessesCWE-200, CWE-489

Technical details

References

Community reviews

Related threats