Varnish/Nginx Proxy Caching
Avoid: vulnerability published 31 Dec 2025 still has no fix after 14 days.
| Ownership | 100 |
|---|---|
| Maintenance | 0 |
| Security | 25 |
| Support | No data |
| Reputation | No data |
Quick answers
- Is Varnish/Nginx Proxy Caching still maintained?
- No. Last release 21 Oct 2019, over 7 years ago. 21 Oct 2019 · wordpress.org
- Who owns Varnish/Nginx Proxy Caching, and has it changed hands?
- No change recorded. 3 Nov 2026 · SVN log
- Was Varnish/Nginx Proxy Caching removed from wordpress.org?
- No. Listed on wordpress.org as of 3 Nov 2026. 3 Nov 2026 · wordpress.org
- Is Varnish/Nginx Proxy Caching safe?
- No. 2 known vulnerabilities have no fix in the current version. 31 Dec 2025 · Wordfence Intelligence
- Is the latest Varnish/Nginx Proxy Caching update safe to install?
- No ownership change before 1.8.3. No one-star spike after it. 21 Oct 2019 · Release history
Active signals
Facts we detected, with links to the source.
- CriticalSEC-2Vulnerability published 31 Dec 2025 still has no fix after 14 days. Disable or replace the plugin. No fix has been released.14 Jan 2026Evidence
- CriticalSEC-2Vulnerability published 20 Aug 2025 still has no fix after 14 days. Disable or replace the plugin. No fix has been released.3 Sep 2025Evidence
- CriticalMNT-1No release in 85 months (last release 21 Oct 2019). Plan a replacement if the plugin is important to your site.20 Oct 2020Evidence
- WarningMNT-2Tested up to WordPress 5.2.30, 19 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.
| razvanstanga | 25 Nov 2015 to 21 Oct 2019, 93 commits |
|---|
1 committer recorded. No ownership change since 2015.
Maintenance
- Last release
- 7 years ago
- Releases, 24 months
- 0
- Tested up to
- 5.2 vs 7.1
- Requires PHP
- 5.2.4 supported 8.2+
| Q1 2024 | 0 |
|---|---|
| Q2 2024 | 0 |
| Q3 2024 | 0 |
| Q4 2024 | 0 |
| Q1 2025 | 0 |
| Q2 2025 | 0 |
| Q3 2025 | 0 |
| Q4 2025 | 0 |
| Q1 2026 | 0 |
| Q2 2026 | 0 |
| Q3 2026 | 0 |
| Q4 2026 | 0 |
Last release 21 Oct 2019. Tested up to 5.2, 19 major versions behind WordPress 7.1.
Reputation
Last 90 days: no reviews. Lifetime: 5.0.
| 5 star | 10 |
|---|---|
| 4 star | 0 |
| 3 star | 0 |
| 2 star | 0 |
| 1 star | 0 |
Security record
2 vulnerabilities in 24 months, 2 with no fix in the current version.
| Published | Issue | CVSS | Affected | Fixed in | Days to patch |
|---|---|---|---|---|---|
| 31 Dec 2025 | Varnish/Nginx Proxy Caching <= 1.8.3 - Unauthenticated Information Exposure | 7.5 | <= 1.8.3 | No fix | n/a |
| 20 Aug 2025 | Varnish/Nginx Proxy Caching <= 1.8.3 - Authenticated (Administrator+) Stored Cross-Site Scripting | 4.4 | <= 1.8.3 | No fix | n/a |
Sources: Wordfence Intelligence, CISA Known Exploited Vulnerabilities, readme changelogs.
Support
Support history appears after our first snapshots of the forum counts.
Momentum
600+ 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.
Facts
| Version | 1.8.3 |
|---|---|
| Author | Razvan Stanga |
| Added | 25 Nov 2015 |
| Last updated | 21 Oct 2019 |
| Active installs | 600+ |
| Requires WordPress | 4.0 |
| Tested up to | 5.2.30 |
| Requires PHP | 5.2.4 |
| Category | Performance & Optimization > Caching Solutions |
| Tags | cache, nginx, Purge, caching, varnish |
Other plugins by this author: Redis Post Views
Questions
Is Varnish/Nginx Proxy Caching still maintained?
No. Last release 21 Oct 2019, over 7 years ago.
Who owns Varnish/Nginx Proxy Caching, and has it changed hands?
No change recorded.
Was Varnish/Nginx Proxy Caching removed from wordpress.org?
No. Listed on wordpress.org as of 3 Nov 2026.
Is Varnish/Nginx Proxy Caching safe?
No. 2 known vulnerabilities have no fix in the current version.
Is the latest Varnish/Nginx Proxy Caching update safe to install?
No ownership change before 1.8.3. No one-star spike after it.