Lenix scss compiler

Lenix scss compiler has 2 disclosed vulnerabilities in the WordSec catalog, all reported in 2025; none of them are fixed as of September 2026. Their average CVSS score is 4.3, and the most serious one scores 4.4 out of 10. 2025 was the busiest year with 2 disclosures.

The most common weakness is Cross-Site Request Forgery (CSRF), behind 1 of the records (50%). Other recurring categories include Cross-Site Scripting.

None of the 2 issues recorded for Lenix scss compiler have a published fix yet, which makes virtual patching the only reliable mitigation. The oldest unresolved one dates back to 2025.

All of these findings were reported by Nabil Irawan. Lenix scss compiler is installed on roughly 800 WordPress sites, so each unpatched flaw has a wide blast radius. The current release is tested up to WordPress 5.9.16.

Strategic Overview

Avg CVSSMedium

4.3/ 10

Patch Coverage0%

Open

Fixed

Get automatic notifications for all Lenix scss compiler vulnerabilities before they are exploited.

Most severe open issueCVSS 4.4CVE-2025-60144

Lenix scss compiler <= 1.2 - Authenticated (Administrator+) Stored Cross-Site Scripting

Read the full analysis

Vulnerability Records

2 records


2025-09-26 00:00	Lenix scss compiler <= 1.2 - Authenticated (Administrator+) Stored Cross-Site Scripting Lenix scss compiler <= 1.2	`CVE-2025-60144`	4.4 Medium	Nabil Irawan	No
2025-09-26 00:00	Lenix scss compiler <= 1.2 - Cross-Site Request Forgery Lenix scss compiler <= 1.2	`CVE-2025-60145`	4.3 Medium	Nabil Irawan	No

Showing 1–2 of 2 reports

Plugin Profile

Latestv1.2

Lenix scss compiler

Author

yonifre

5.0(3)

100/100

Last Updated

2022-05-21 (4y ago)

Active Installs

800+

Downloads

6,483

Requires WP

3.8+

Requires PHP

Tested up to

WP 5.9.16

Created

2017-08-31 (9y ago)

A useful plugin for developers writing SCSS. The plugin allows you to write SCSS directly on the server (via FTP) without the need for a local compiler. How It Works? Choose a source folder for SCSS and a target folder for CSS. Write the SCSS code in the file on the source folder, and it automatically creates a CSS file in the target folder. What’s included? Option for multiple source and destination folders. Allows you to set a folder in the entire wp-content space. Performance – only when one of the source files change – it re-compiling itself. After development you can turn off / delete the plugin without fear, and all the files are stay where they were. Allows you to develop a theme and plugin at the same time. Example: source: themes/your-theme/assets/scss/style.scss body { color: black; .main { background: red; } } target: themes/your-theme/assets/css/style.css body { color: black; } body .main { background: red; } — pay attention! If the file already exists in the destination folder – it will be overwritten by the SCSS file

View on WordPress.org