CVE-2026-40736
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 · uneditedUnauthenticated PHP Object Injection in Laurits <= 1.5.1 versions.
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 confidenceUnauthenticated PHP Object Injection vulnerability in Laurits CMS version 1.5.1 and below allows remote attackers to inject malicious PHP objects by supplying serialized data, potentially leading to remote code execution through deserialization gadget chains.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/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.
-
Identify Laurits CMS versionLocate the version file or header in the Laurits installation. Common locations include a version.php file, CHANGELOG.txt, or the admin dashboard. Run: find /path/to/laurits -name 'version*' -o -name 'CHANGELOG*' 2>/dev/null | xargs grep -i 'version\|1\.5' 2>/dev/nullAffected if The installed version is 1.5.1 or any version below 1.5.1
-
Find PHP deserialization entry pointsSearch the Laurits source code for usage of PHP unserialize() function without prior sanitization. Run: grep -r 'unserialize\|__destruct\|__wakeup' /path/to/laurits --include='*.php' 2>/dev/nullAffected if The application code contains unserialize() calls on user-controlled input without validation
-
Identify exposed endpoints accepting serialized dataReview web server access logs and Laurits source for PHP scripts that process $_GET, $_POST, or $_COOKIE parameters through unserialize(). Check common entry points like index.php, ajax handlers, or API endpoints. Run: grep -r '\$_GET\|\$_POST\|\$_COOKIE' /path/to/laurits --include='*.php' 2>/dev/null | grep -i 'unserialize'Affected if Any HTTP-accessible endpoint passes request parameters directly to unserialize()
-
Check for deserialization gadget classesSearch the Laurits installation for known PHP deserialization gadget classes (common patterns: __destruct, __wakeup, __toString methods in libraries. Run: grep -r 'function __destruct\|function __wakeup\|function __toString' /path/to/laurits --include='*.php' 2>/dev/nullAffected if The application contains magic methods that could be chained for RCE during deserialization
-
Verify network exposureDetermine if the Laurits application is directly accessible from the internet or unauthenticated networks. Check web server vhost configuration or firewall rules. Run: curl -I http://your-laurits-site/ 2>/dev/nullAffected if The vulnerable Laurits installation is reachable without authentication from untrusted networks
If Laurits CMS version 1.5.1 or below is running and has PHP endpoints that accept and unserialize user-supplied data without validation, the environment is affected by this PHP Object Injection 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 dataUpdate Laurits to a version beyond 1.5.1 once available; if no patch exists, disable the application or restrict network access until a fix is released.
- 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-2026-40736 — 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-40736 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