CVE-2026-27436
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 · uneditedEditor Arbitrary Code Execution in Five Star Business Profile and Schema <= 2.3.19 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 · high confidenceThe Five Star Business Profile and Schema WordPress plugin versions 2.3.19 and below contains a critical vulnerability allowing users with Editor-level privileges to execute arbitrary PHP code on the server, likely due to insufficient input validation in admin functionality.
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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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 the installed plugin versionLog into WordPress admin and navigate to Plugins > Installed Plugins, or run `wp plugin list --slug=five-star-business-profile` if WP-CLI is available, or inspect the plugin main file header in wp-content/plugins/five-star-business-profile-and-schema/five-star-business-profile-and-schema.php for the Version commentAffected if The displayed version is 2.3.19 or lower
-
Confirm plugin is activeVerify the Five Star Business Profile and Schema plugin is currently activated in the Plugins list in WordPress adminAffected if The plugin shows as Active and the version is 2.3.19 or lower
-
Identify Editor-level usersGo to Users > All Users in WordPress admin and filter or check for users with the Editor role, or run `wp user list --role=editor` with WP-CLIAffected if Any Editor-level user accounts exist in the WordPress installation
-
Review for unauthorized code execution artifactsCheck wp-content/uploads/, wp-content/plugins/, and the theme directory for suspicious PHP files with random names, encoded payloads, or files created/modified after the expected timeline. Also review access logs for POST requests to plugin endpoints from Editor usersAffected if Suspicious PHP files are found or logs show code execution patterns from Editor-level accounts
You are affected if the Five Star Business Profile and Schema plugin version is 2.3.19 or lower AND at least one Editor-level user account exists in your WordPress installation.
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 Five Star Business Profile and Schema plugin to the latest patched version immediately. If no patched version is available, disable or remove the plugin and audit all Editor-level user accounts for potential compromise.
- 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-2026-27436 — 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-27436 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