CVE-2026-36521
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 · uneditedPublicCMS V5.202506.d has a Cross Site Scripting (XSS) vulnerability in the site configuration management module.
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 · moderate confidencePublicCMS V5.202506.d contains a Cross Site Scripting (XSS) vulnerability in the site configuration management module. With a CVSS score of 6.1, this is a network-exploitable, medium-severity issue that could allow attackers to inject malicious scripts into the CMS interface.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 installed PublicCMS versionLocate the version identifier in the CMS installation (typically in an about page, admin dashboard, or version file within the application root). Compare it to V5.202506.d.Affected if The installed version is V5.202506.d or falls within the V5.202506.x release line prior to patching.
-
Confirm site configuration module is accessibleDetermine whether the site configuration management module is enabled and accessible within the CMS admin interface.Affected if The site configuration management module is present and accessible to users with administrative privileges.
-
Inspect site configuration input fieldsNavigate to the site configuration management section in the admin panel and examine available input fields (e.g., site name, description, custom fields).Affected if Input fields in the site configuration module accept user-supplied content without visible sanitization indicators.
-
Test for reflected content in configuration outputsSubmit a harmless test string (such as <script>alert(1)</script> or a benign HTML tag) in a site configuration field and view the rendered page source or admin interface to see if the raw tags appear.Affected if The submitted test string renders as interpreted HTML or JavaScript in the site configuration output, indicating missing output encoding.
If running PublicCMS version V5.202506.d with the site configuration management module accessible and inputs are reflected unencoded in output, the environment is affected by this XSS vulnerability.
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.
From vendor dataImplement proper input validation and output encoding in the site configuration management module to neutralize malicious script payloads.
- Consultation3.0 h
- Implementation6.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36521 — 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-2026-36521 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