WordPress Core < 2.2.3 - Restriction Bypass

Reaching this weakness in WordPress 2.2 <= 2.2.2 takes a caller who can reach the endpoint. Improper access control means the code decides what a caller may do using something other than their actual permissions, so the decision can be wrong without any check appearing to be missing.

Whoever can shape the request decides the answer, so the protected action runs for callers the code never meant to allow. For WordPress 2.2 the fix is 2.2.3: builds <= 2.2.2 are affected, anything from 2.2.3 onward is not.