CVE-2025-69130
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 · uneditedSubscriber PHP Object Injection in Entrepreneur - Booking for Small Businesses WordPress Theme <= 3.1.3 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 confidenceA PHP Object Injection vulnerability exists in the Entrepreneur WordPress theme allowing authenticated users with subscriber-level privileges to inject arbitrary PHP objects. This can potentially be chained with magic methods to achieve remote 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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 Entrepreneur theme is installedIn WordPress admin, go to Appearance > Themes. Look for 'Entrepreneur - Booking for Small Businesses' theme in the list of installed themes.Affected if The Entrepreneur theme appears in the installed themes list
-
Check the installed theme versionClick on the Entrepreneur theme details. Look for the version number displayed in the theme information panel. Alternatively, check the style.css file in the theme directory for the 'Version:' comment header.Affected if The version listed is 3.1.3 or lower
-
Verify subscriber-level user accounts existIn WordPress admin, go to Users > All Users. Review the list to see if any users have the 'Subscriber' role assigned.Affected if At least one user with Subscriber role exists in the WordPress installation
-
Check if the vulnerable deserialization is reachableExamine the theme files for PHP code that uses unserialize() on user-controlled input, particularly in files that handle user submissions or AJAX requests. Look for $_GET, $_POST, or $_REQUEST variables passed to unserialize(). Search theme files for patterns like 'unserialize($_POST' or 'unserialize($_REQUEST'.Affected if Code uses unserialize() on input that could be controlled by any authenticated user including subscribers
You are affected if the Entrepreneur theme version is 3.1.3 or lower AND subscriber-level users exist AND the theme contains vulnerable unserialize() calls on user-controlled input.
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 Entrepreneur - Booking for Small Businesses theme to version 3.1.4 or later. If no patch is available, disable and replace the theme.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-69130 — 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-2025-69130 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