CVE-2026-35173
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, an IDOR / Mass Assignment issue exists in the Post model that allows authenticated users with post editing permissions (Edit Post, Edit Draft, Edit Own Post, Edit Own Draft) to modify posts they do not own and do not have permission to edit. By passing internal class properties such as id into the post_attributes payload, an attacker can alter the object being instantiated. As a result, further actions are performed on another user’s post rather than the attacker’s own post, effectively enabling post takeover. 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 confidenceChyrp Lite prior to 2026.01 contains an IDOR/Mass Assignment vulnerability in the Post model. Authenticated users with post editing permissions can manipulate the post_attributes payload by injecting internal properties like id, causing the application to modify the wrong post object. This allows unauthorized post takeover of any post the attacker does not own.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 Chyrp Lite versionLocate the version file or constant in your Chyrp Lite installation. Common locations include a VERSION file in the root directory, a version constant in includes/config.php, or the version field in composer.json. Compare the found version to 2026.01.Affected if The installed version is anything earlier than 2026.01 (e.g., 2025.x, earlier).
-
Verify user has post editing permissionsCheck if the application has any registered users with post editing privileges. Log into the admin panel or inspect the users table in the database to identify accounts with post editing capabilities.Affected if There exists at least one user account with post editing permissions, making the IDOR exploitable if the version is vulnerable.
-
Examine Post model mass assignment handlingInspect the Post model class file (typically in includes/model/Post.php or similar) for the __construct or __set methods that handle post_attributes. Check if internal properties like 'id', 'user_id', or 'created_at' can be set through user-supplied post_attributes data.Affected if The Post model allows mass assignment of internal properties such as 'id' through the post_attributes parameter without strict filtering.
-
Review post editing endpoint logicLocate the controller or handler that processes post edits (often in modules or actions handling post updates). Trace how the post_attributes payload is passed to the Post model and whether the 'id' field can be overridden.Affected if The post edit functionality accepts and processes an 'id' or other internal property from the post_attributes payload, allowing manipulation of unintended post records.
Your environment is affected if you are running any version of Chyrp Lite prior to 2026.01 AND have users with post editing permissions, combined with the Post model allowing internal property injection via post_attributes.
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 Chyrp Lite version 2026.01 or later. If upgrading is not immediately feasible, implement mass-assignment protection in the Post model by restricting which properties can be set via user input, limiting assignment to only intended user-facing fields.
2026.01
- 1. Back up your entire Chyrp Lite installation including database and configuration files
- 2. Download Chyrp Lite version 2026.01 from the official GitHub repository
- 3. Replace the existing Chyrp Lite files with the new version 2026.01 files
- 4. Preserve your configuration file (config.php or equivalent) and any custom themes or modules during the upgrade
- 5. Verify the application functions correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35173 — 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-35173 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