CVE-2026-35174
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 · uneditedChyrp Lite is an ultra-lightweight blogging engine. Prior to 2026.01, a path traversal vulnerability exists in the administration console that allows an administrator or a user with Change Settings permission to change the uploads path to any folder. This vulnerability allows the user to download any file on the server, including config.json.php with database credentials and overwrite critical system files, leading to remote code execution. This vulnerability is fixed in 2026.01.
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 confidencePath traversal vulnerability in Chyrp Lite admin console allows users with Change Settings permission to modify the uploads path to arbitrary locations, enabling unauthorized file download (including config.json.php with database credentials) and system file overwrite, leading to remote code execution.
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< 2026.01CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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.
-
Check installed Chyrp Lite versionLocate the version file or check the admin dashboard for the current Chyrp Lite version numberAffected if The installed version is earlier than 2026.01
-
Verify admin console access existsConfirm you have access to the Chyrp Lite admin console at /adminAffected if You can log into the admin console with an account that has Change Settings permission
-
Inspect the uploads path settingNavigate to admin settings and examine the current uploads/ uploads_path configuration valueAffected if The uploads path setting allows directory traversal sequences (such as ../../) or points outside the intended uploads directory
-
Test for sensitive file accessibilityAttempt to access the uploads path with traversal sequences targeting config.json.php or similar configuration filesAffected if You can successfully read sensitive files outside the intended uploads directory through this setting
You are affected if your Chyrp Lite installation is version earlier than 2026.01 AND you have an admin account with Change Settings permission that can access and modify the uploads path setting.
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 · scoped2026.01
Upgrade to version 2026.01 or later; restrict admin permissions and audit users with Change Settings capability until the patch is applied.
2026.01
- 1. Create a complete backup of your current Chyrp Lite installation, including the database and all files.
- 2. Download Chyrp Lite version 2026.01 from the official GitHub repository or distribution source.
- 3. Extract the downloaded package.
- 4. Replace the existing Chyrp Lite files with the new version 2026.01 files, preserving your configuration and content data.
- 5. Verify the upgrade was successful by accessing the admin console.
- 6. Confirm that the uploads path setting now properly validates and restricts paths, preventing the path traversal vulnerability.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35174 — 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-35174 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