CVE-2022-35118
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 · uneditedPyroCMS v3.9 was discovered to contain multiple cross-site scripting (XSS) vulnerabilities.
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 confidencePyroCMS v3.9 contains multiple cross-site scripting (XSS) vulnerabilities, allowing attackers to inject malicious scripts into web pages viewed by other users. The CVSS 6.1 score indicates the vulnerabilities are exploitable but require user interaction.
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<= 3.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
- 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.
-
Confirm PyroCMS installation existsLook for the PyroCMS installation directory structure. Common indicators: presence of 'streams' folder in vendor/, or characteristic PyroCMS template files in themes/. Check the web root for 'index.php' that initializes PyroCMS.Affected if PyroCMS is installed and the characteristic directory structure is found.
-
Identify the installed PyroCMS versionCheck the version file. In PyroCMS 3.x, the version is typically defined in the main composer.json file in the web root, or in a version.php within the system or vendor directories. Look for a 'version' field or tag.Affected if The discovered version is 3.9 or any version number lower than 3.9.
-
Locate user-facing form inputs and content rendering areasIdentify custom addons, themes, or modules that render user-submitted content. Check the views/ and themes/ directories for blade or PHP template files that accept and display user input. Look for form fields in admin panels and public-facing pages.Affected if Custom or third-party addons exist that accept user input and render it without visible sanitization wrappers.
-
Inspect for missing output encoding in templatesExamine the template files identified in the previous step. Look for direct output of user variables using double curly braces {{ }} or raw PHP echo statements without using PyroCMS stream field encoding methods or htmlspecialchars().Affected if Templates output user-provided data using raw echo statements or unescaped variable interpolation without encoding functions.
You are affected if PyroCMS version 3.9 or lower is installed AND user-facing input fields exist that lack output encoding in their templates.
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 output encoding and input sanitization across all user-facing fields, particularly in form inputs and content rendering areas. Apply Content-Security-Policy headers to mitigate XSS execution.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-35118 — 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-35118 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