CPSA ยท Web servers, architecture and protocols
HTML and XML
Structure, forms, entities and security-relevant features such as external entities.
Key points
- HTML forms (<form>, <input>): send data via GET or POST; hidden fields, comments, inline scripts show in the source.
- XML: strict, extensible data format (SOAP, config files, feeds).
- Entities (& or user-defined): replaced by values when parsed.
- XML External Entity (XXE): a weak parser resolves entities to local files or internal URLs from untrusted input: file disclosure, SSRF, DoS.
- Fix: disable DTDs and external entities.
Source: https://community.owasp.org/vulnerabilities/XML_External_Entity_(XXE)_Processing
Practice questions
What does XXE stand for?
- XML External Entity
- Extended XSS Exploit
- XML Extension Encoding
- Cross-Execution eXploit
Show answer
Answer: A. XML External Entity
XXE is XML External Entity processing: the parser resolves entities defined outside the document. The other expansions are not standard terms.
Which measures reduce XXE risk in an XML-processing application?
- Disable DTD processing in the parser
- Disable resolution of external entities
- HTML-encode the page title
- Use a longer session timeout
- Hide the Server header
Show answer
Answer: A. Disable DTD processing in the parser, B. Disable resolution of external entities
Disabling DTDs and external entities removes the mechanism. Blocking nothing and escaping output for HTML do not stop a parser from resolving entities.
True or false: an <input type="hidden"> field cannot be changed by the user, because it is not shown on the page.
Show answer
Answer: False
False. Hidden only affects display; the value is in the source and can be edited with developer tools or an intercepting proxy, so the server must not trust it.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.

More CPSA topics in this module
- Web server operation, virtual hosting and proxies
- IIS and Apache and their typical flaws
- Tiered web architectures
- HTTP methods and response codes
- HTTPS, SOAP and security-related headers
- Server-side and client-side web languages
- Application servers and frameworks
- Server extension interfaces
- Thin and thick web clients, applets and decompilation