CVE-2022-1536
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability has been found in automad up to 1.10.9 and classified as problematic. This vulnerability affects the Dashboard. The manipulation of the argument title with the input Home</title><script>alert("home")</script><title> leads to a cross site scripting. The attack can be initiated remotely but requires an authentication. The exploit details have disclosed to the public and may be used.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceStored XSS vulnerability in Automad Dashboard where the title parameter is not properly sanitized before rendering, allowing injection of malicious JavaScript via payload `</title><script>alert("home")</script><title>`. The attack requires authentication but can be exploited remotely.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.10.9CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Automad installation and versionLocate the Automad installation directory and check the version number in the core package file (such as composer.json or a version file in the installation root)Affected if The installed version is 1.10.9 or lower
-
Confirm Dashboard access is enabledCheck the Automad configuration files for Dashboard-related settings or routes that enable the administrative interfaceAffected if The Dashboard feature is accessible and authentication is available
-
Verify title parameter handling in Dashboard viewsInspect Dashboard template files that render the title parameter to see if output encoding is applied before displaying user-supplied title contentAffected if The title parameter is rendered without HTML entity encoding or sanitization
-
Check for stored malicious payloadsIf you have access to the database or content storage, search for the specific payload pattern `</title><script>` or similar XSS vectors in any stored title fieldsAffected if The payload is found stored in the system without being sanitized or encoded
You are affected if Automad version 1.10.9 or lower is installed, the Dashboard is accessible, and the title parameter in Dashboard views renders user-supplied content without proper HTML encoding.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedImplement proper input validation and output encoding for the title parameter in Dashboard views. Apply HTML entity encoding before rendering user-supplied content to prevent script execution.
Automad 1.10.10 or later (verify exact version via official release notes)
- Check the Automad GitHub releases page or official changelog to confirm the exact version containing the XSS fix for CVE-2022-1536
- Download or update to the confirmed fixed version (1.10.10 or later)
- Log in to the Automad Dashboard and verify the title parameter is now properly sanitized (no script tags should execute)
- Test by attempting to inject a benign script payload in the title field to confirm the fix works
- Ensure the upgrade is applied to all production instances
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1536 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-1536 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data