OWASP-ASVS-4.0-testing-guide | Cybersecurity library

I would think the "assumptions" paragraph and the "Attack narrative" paragraph are somehow overlapping. I would use the "Assumptions" paragraph to state a couple of high level decisions made before starting the attack, with whatever little information the pentester would have on the attack. I would expand on the tools and techniques used in the "Attack narrative" paragraph

For example an assumption could be: "The pentester is carrying on the exercise against the infrastructure of a soho company with less than 5 people It is common for soho companies to use consumer networking equipment that is usually unsecure, and left configured as defualt. For this reason the attacker focused on scanning for http and ssh using a database of vendors default username and passwords"

Yes, it is possible. The point of having exported symbols in shared libraries is to be able to use them - after all. In C, you can do this either by linking the library to the application (not really an option for python), or runtime loading the library and finding the required symbol (on linux: dlopen, dlsym). The manpage example shows how to do this in C.

The issue was caused and fixed as follows -

The button that takes XML file as input in the HTML form has an inline event handler, which the CSP Policy was blocking, thereby blocking the upload. I moved this inline event handler to an external function and called the function. This fixed the issue and CSP is no longer blocking the function.