{"uuid": "277acfc5-be96-479a-bdc9-f2096cd09e6a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-24947", "type": "published-proof-of-concept", "source": "https://t.me/hacking_Attack/51195", "content": ".  That means that the fuzzer detected executing fopen() on a known payload.  Most of the payloads contain the word GARLIC in them to facilitate automatic  detection in output. You may see or configure them in docker_image/magic_payloads.php.  Then, you may browse the source code and see that indeed the wp_ajax_rvm_import_markers  endpoint uses the file content to render output, thus allowing you to read arbitrary files  on the server: CVE-2021-24947 (https://wpscan.com/vulnerability/c6bb12b1-6961-40bd-9110-edfa9ee41a18).  What you see in white is a crash considered interesting (you may modify them or add new ones  in crash_detectors.py). Green is the context. In blue you see the report file name  (with plugin name), plugin popularity and endpoint name (here: the ajax action name).  The data in yellow are what payloads were injected into what variables.  Reflected XSS  Let's assume you are fuzzing page-builder-add in version 1.4.9.4:  ./bin/fuzz_plugin page-builder-add --version 1.4.9.4    After printing the results, you will see known payload echoed back:\n\n___________________________ \n@hacking_Attack\n@Hacking_Video", "creation_timestamp": "2026-09-06T00:00:14.038947Z"}