Safeguard
Vulnerability Analysis•

CVE-2022-1609: Critical Backdoor in School Management Plugin

CVE-2022-1609 is a critical backdoor in the School Management WordPress plugin, scored 9.8, giving PHP execution. Update to 9.9.7 and investigate.

Safeguard Security Team
3 min read

CVE-2022-1609 is a critical severity backdoor in the School Management WordPress plugin, scored 9.8 by NVD. An obfuscated REST API handler in the license checking code lets an unauthenticated attacker run PHP. The fix is version 9.9.7, and sites that ran earlier versions should be investigated.

What's affected

The record says the School Management plugin before 9.9.7 contains an obfuscated backdoor injected in its license checking code. It registers a REST API handler that lets an unauthenticated attacker execute arbitrary PHP code on the site. The vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

WPScan's entry, published 2022-05-18, lists the affected plugin as school-management-pro and the fixed version as 9.9.7. It credits the finding to the Jetpack Scan team along with WordPress support staff.

The sources differ slightly on score. NVD gives 9.8 Critical and WPScan gives 10.0 Critical. Both are the top of the scale, and both agree on the fixed version.

Weakness class: CWE-94.

How to check if you're exposed

With WP-CLI you can read the version of the commercial plugin with:

wp plugin list --fields=name,status,version | grep -i school

Otherwise read it from the Plugins page. Anything before 9.9.7 is in range. Because the code is described as a backdoor, a version check is not enough: a site that ran an affected version should also be checked for signs of abuse, such as files you did not add, unknown admin users and unexplained scheduled tasks.

What to do now

  1. Find every site that has School Management Pro installed.
  2. Update to 9.9.7 or later.
  3. Treat any site that ran an older version as possibly compromised and have it reviewed: file integrity, admin users, scheduled tasks, database changes.
  4. Rotate administrator, database and API credentials stored on the server.
  5. Restore from a backup taken before the affected version was installed if you find evidence of misuse.

Why it matters

This is a supply chain problem in the plain sense. The malicious code is not an accident in a feature. The record describes it as a backdoor injected into the license check, a part of the plugin that most buyers never read. The weakness class is CWE-94, code injection.

The practical lesson for site owners is that patching removes the code but does not undo what an attacker may have done while it was there. Unauthenticated remote execution means no password was needed, so there may be no obvious trace in login records.

For commercial plugins that you cannot easily audit, monitoring matters: file integrity checks, an allowlist for outbound connections and alerts on new admin accounts.

This CVE is not listed in the CISA Known Exploited Vulnerabilities catalog, and none of the pages I read state that it is exploited in the wild. That is a statement about what is known, not a reason to delay the fix.

Try it yourself

Click through it at your own pace, or open it full screen.

Quick check

Is a plugin update enough?

It removes the backdoor code but does not tell you whether the site was already used. Review sites that ran an older version.

Do attackers need a login?

No. The record says an unauthenticated attacker can execute PHP through a REST API handler.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.