CVE-2026-39655
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 TeconceTheme Mayosis Core allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects Mayosis Core: from n/a through 5.4.7.
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 TeconceTheme Mayosis Core allows attackers to access functionality without proper authentication or authorization checks due to incorrectly configured access control security levels. This affects Mayosis Core versions up to and including 5.4.7, potentially allowing unauthorized users to perform actions that should be restricted to authenticated users with proper capabilities.
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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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 if Mayosis Core theme is installedLocate the theme folder in wp-content/themes/ and check for mayosis or teconce theme directories. Check theme style.css header for the theme name and version, or query via WordPress admin appearance section.Affected if The Mayosis Core theme by Teconce is present in the WordPress installation.
-
Determine installed theme versionOpen the style.css file in the theme directory and locate the 'Version:' header in the CSS comment block at the top, or check via WordPress admin under Appearance > Themes.Affected if The version number is 5.4.7 or lower.
-
Test for unauthorized endpoint accessSend direct HTTP requests to common Mayosis Core AJAX endpoints (such as /wp-admin/admin-ajax.php?action=mayosis_...) or any custom Mayosis-specific REST API routes without providing authentication credentials or valid nonces.Affected if Sensitive data or privileged actions are returned or executed without requiring authentication or authorization validation.
-
Verify access control on theme core featuresInspect the theme core files (typically in includes/ or core/ folders) for functions handling user data, content export, settings modification, or file uploads. Check if these functions include current_user_can() or similar authorization checks before executing sensitive operations.Affected if Critical functions lack proper capability checks or role-based access validation.
A user is affected if the Mayosis Core theme version is 5.4.7 or lower AND sensitive theme endpoints or core functionality can be accessed or executed without authentication or proper authorization validation.
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 dataImplement proper authorization checks (capability checks and nonce verification) on all sensitive functions and AJAX endpoints within Mayosis Core. Review and enforce WordPress capability requirements for all user-facing functionality.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39655 — 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-39655 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