The requestKeywordDenylist security control can be bypassed by placing any nested object or array before a prohibited keyword in the request payload. This is caused by a logic bug that stops scanning sibling keys after encountering the first nested value. Any custom requestKeywordDenylist entries configured by the developer are equally by-passable using the same technique.
All Parse Server deployments are affected. The requestKeywordDenylist is enabled by default.
The fix replaces the recursive object scanner with an iterative stack-based traversal that processes all nested values without prematurely exiting the scan loop. This also eliminates a potential stack overflow on deeply nested payloads.
Use a Cloud Code beforeSave trigger to validate incoming data for prohibited keywords across all classes.
{
"github_reviewed": true,
"github_reviewed_at": "2026-03-10T00:57:37Z",
"cwe_ids": [
"CWE-693"
],
"severity": "MODERATE",
"nvd_published_at": "2026-03-10T18:18:53Z"
}