CVE-2024-12312
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 · uneditedThe Print Science Designer plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.3.152 via deserialization of untrusted input through the 'designer-saved-projects' cookie. This makes it possible for unauthenticated attackers to inject a PHP Object. No known POP chain is present in the vulnerable software. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.
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 confidenceThe Print Science Designer WordPress plugin is vulnerable to PHP Object Injection through deserialization of untrusted data from the 'designer-saved-projects' cookie. An unauthenticated attacker can inject serialized PHP objects via this cookie, and while no POP chain exists in the plugin itself, one could be present via other installed plugins or themes, potentially enabling arbitrary file deletion, data retrieval, or code execution.
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.
-
Confirm Print Science Designer plugin is installedCheck the WordPress plugins directory for a folder named 'print-science-designer' or similar. On the server, list wp-content/plugins/ directory contents, or use WordPress admin_plugins page or wp-cli: wp plugin listAffected if The plugin folder exists in wp-content/plugins/
-
Identify the installed plugin versionOpen the main PHP file of the plugin and locate the plugin header comment containing 'Version:', or run: wp plugin get print-science-designer --field=versionAffected if Installed version is 1.3.152 or lower
-
Verify the vulnerable cookie handling is presentSearch the plugin files for deserialization of the 'designer-saved-projects' cookie. Run: grep -r 'designer-saved-projects' wp-content/plugins/ or inspect plugin PHP files for code handling this cookie with unserialize()Affected if Plugin code contains unserialize() called on $_COOKIE['designer-saved-projects'] or similar user-controlled input
-
Check for potential POP chain sourcesReview other installed plugins and themes for known PHP Object Injection vulnerabilities or exploitable magic methods. Use wp plugin list to see all installed pluginsAffected if Multiple additional plugins are installed, particularly any known to contain PHP Object Injection POP chains
Environment is affected if Print Science Designer plugin version 1.3.152 or lower is installed and actively processing the 'designer-saved-projects' cookie through deserialization; the presence of other plugins with exploitable POP chains greatly increases the severity of this 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 the Print Science Designer plugin to a version beyond 1.3.152. If no patched version is available, disable the plugin. Consider minimizing installed plugins/themes to reduce the risk of an external POP chain being present.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12312 — 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-2024-12312 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