CVE-2026-28104
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 · uneditedMissing Authorization vulnerability in Aryan Shirani Bid Abadi Site Suggest site-suggest allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Site Suggest: from n/a through <= 1.3.9.
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 confidenceMissing authorization vulnerability in the Site Suggest WordPress plugin (versions <=1.3.9) allows users to access functionality that should be constrained by Access Control Lists (ACLs). An attacker with low or no privileges can potentially access administrative or privileged functions due to missing permission checks on specific endpoints or actions within the plugin.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
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.
-
Verify Site Suggest plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'site-suggest' or similar, or look for Site Suggest in the WordPress admin under Plugins > Installed PluginsAffected if The plugin folder exists in the WordPress installation
-
Check the installed version numberOpen the main plugin PHP file (typically site-suggest.php) and locate the plugin header comment containing 'Version: x.x.x', or view the version directly in the WordPress admin plugins listAffected if The reported version is 1.3.9 or lower
-
Confirm the plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and verify Site Suggest shows as 'Active'Affected if The plugin is both installed AND active with a vulnerable version
-
Identify exposed sensitive endpoints (if any)Review the plugin source code for PHP files containing add_action or add_api_route calls that handle admin-level functions without capability checks (look for missing current_user_can() or check_admin_referer() calls)Affected if The plugin code contains admin actions or AJAX endpoints that perform privileged operations without authorization validation
Your environment is affected if Site Suggest plugin is installed, active, and running version 1.3.9 or lower, as the missing authorization checks allow low-privilege users to access privileged functionality.
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 to the latest version of Site Suggest when a patch is released, or implement proper authorization checks (checking user capabilities/roles) before executing sensitive functionality.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28104 — 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-28104 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