NPS computy vulnerabilities
Plugin slug nps-computy · 4 known vulnerabilities · latest disclosed 2026-02-04 · WordPress.org page
Every listed vulnerability has a fix. Version 2.8.3 or later is not affected by any of them. If your site runs an older version, update it.
1 of 4 rated high or critical (CVSS 7 or more).
Known vulnerabilities in NPS computy
| Severity | Affected versions | Fixed in | CVE | Published | Details |
|---|---|---|---|---|---|
| High 7.2 | <= 2.8.2 | 2.8.3 | CVE-2025-67984 | 2026-02-04 | Advisory |
| Medium 6.1 | <= 2.8.0 | 2.8.1 | CVE-2024-11807 | 2024-12-03 | Advisory |
| Medium 4.3 | <= 2.7.5 | 2.7.6 | CVE-2024-1755 | 2024-03-25 | Advisory |
| Medium 4.4 | <= 2.7.5 | 2.7.6 | CVE-2024-1754 | 2024-03-25 | Advisory |
Check if a site is affected
Enter a site address to see which version of NPS computy and other plugins it runs, and whether they match a known vulnerability.
Questions
Is the NPS computy plugin safe to use?
All 4 known issues are fixed in current versions (2.8.3 or later). Keeping it updated is what matters.
How do I check which version of NPS computy my site runs?
In WordPress go to Plugins > Installed Plugins. From the outside, the free PluginPeek scan below reads the version from the site's public files.
How do I fix a vulnerable plugin?
Make a full backup, then update it from Dashboard > Updates and check the site afterwards. If you would rather not, we can do it for a fixed $99, paid after you have checked the site.