SCSS WP Editor
Healthy: maintained, last release 20 May 2026, 5 releases in 24 months, no unpatched vulnerabilities.
Tested up to WordPress 6.9.11, 2 major versions behind 7.1.4.
| Ownership | 100 |
|---|---|
| Maintenance | 70 |
| Security | 95 |
| Support | No data |
| Reputation | No data |
Quick answers
- Is SCSS WP Editor still maintained?
- Yes. Last release 20 May 2026, 5 releases in the last 24 months. 20 May 2026 · wordpress.org
- Who owns SCSS WP Editor, and has it changed hands?
- No change recorded. Main committer itpathsolutions since Jan 2022. 3 Nov 2026 · SVN log
- Was SCSS WP Editor removed from wordpress.org?
- No. Listed on wordpress.org as of 3 Nov 2026. 3 Nov 2026 · wordpress.org
- Is SCSS WP Editor safe?
- 1 known vulnerability, fixed (latest in 1.2.2). Not on the exploited list. 1 Apr 2025 · Wordfence Intelligence
- Is the latest SCSS WP Editor update safe to install?
- No ownership change before 1.2.3. No one-star spike after it. 20 May 2026 · Release history
Active signals
Facts we detected, with links to the source.
- WarningMNT-2Tested up to WordPress 6.9.11, 2 major versions behind 7.1.4. Plan a replacement if the plugin is important to your site.3 Nov 2026Evidence
Ownership timeline
Who commits to the plugin's code on wordpress.org, over time.
| plugin-master | 17 Jan 2022 to 17 Jan 2022, 1 commits |
|---|---|
| itpathsolutions | 18 Jan 2022 to 20 May 2026, 29 commits |
2 committers recorded. No ownership change since 2022.
Maintenance
- Last release
- 6 months ago
- Releases, 24 months
- 5
- Tested up to
- 6.9 vs 7.1
- Requires PHP
- 8.2 supported 8.2+
| Q1 2024 | 0 |
|---|---|
| Q2 2024 | 2 |
| Q3 2024 | 0 |
| Q4 2024 | 0 |
| Q1 2025 | 0 |
| Q2 2025 | 0 |
| Q3 2025 | 0 |
| Q4 2025 | 3 |
| Q1 2026 | 0 |
| Q2 2026 | 2 |
| Q3 2026 | 0 |
| Q4 2026 | 0 |
Last release 20 May 2026. Tested up to 6.9, 2 major versions behind WordPress 7.1.
Reputation
Last 90 days: no reviews. Lifetime: 5.0.
| 5 star | 4 |
|---|---|
| 4 star | 0 |
| 3 star | 0 |
| 2 star | 0 |
| 1 star | 0 |
Security record
1 vulnerability in 24 months, patched (latest fixed in 1.2.2).
Show 1 patched vulnerability
| Published | Issue | CVSS | Affected | Fixed in | Days to patch |
|---|---|---|---|---|---|
| 1 Apr 2025 | SCSS WP Editor <= 1.2.1 - Cross-Site Request Forgery | 4.3 | <= 1.2.1 | 1.2.2 | n/a |
Sources: Wordfence Intelligence, CISA Known Exploited Vulnerabilities, readme changelogs.
Support
Support history appears after our first snapshots of the forum counts.
Momentum
800+ active installs. History builds with each weekly snapshot.
Momentum history builds with each snapshot.
Healthier alternatives
Same job, rated Healthy, higher Canary Score and at least 10,000 installs. Never sponsored.
No healthier plugin in the same category yet.
Facts
| Version | 1.2.3 |
|---|---|
| Author | IT Path Solutions |
| Added | 18 Jan 2022 |
| Last updated | 20 May 2026 |
| Active installs | 800+ |
| Requires WordPress | 6.0 |
| Tested up to | 6.9.11 |
| Requires PHP | 8.2 |
| Category | Design & Themes > Themes & Templates |
| Tags | scss, css editor, custom scss, scss editor, scss to css |
Other plugins by this author: Contact Form to Any API, Gift Pack for WooCommerce, Connect WPForm to Any API, Product Image Editor with Canva for WooCommerce, AccessDoor - Smart Admin Login & Security, ErrorWatcher
Questions
Is SCSS WP Editor still maintained?
Yes. Last release 20 May 2026, 5 releases in the last 24 months.
Who owns SCSS WP Editor, and has it changed hands?
No change recorded. Main committer itpathsolutions since Jan 2022.
Was SCSS WP Editor removed from wordpress.org?
No. Listed on wordpress.org as of 3 Nov 2026.
Is SCSS WP Editor safe?
1 known vulnerability, fixed (latest in 1.2.2). Not on the exploited list.
Is the latest SCSS WP Editor update safe to install?
No ownership change before 1.2.3. No one-star spike after it.