The vulnerability stems from improper input sanitization in the Markdown processing pipeline. The PostController's save action handles user input from the blog editor, and the Markdown parser (likely using a library like Parsedown) converts this input to HTML. The provided XSS payload (<svg/onrandom=random onload=confirm(1)>) indicates the system allows SVG elements with event handlers to persist through parsing/sanitization. These functions are core to content processing and would logically be responsible for the inadequate neutralization described in CWE-79. The high confidence comes from the vulnerability's nature (XSS in Markdown rendering) and Pagekit's architecture patterns.