CVE-2026-32338
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 raratheme Construction Landing Page construction-landing-page allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Construction Landing Page: from n/a through <= 1.4.1.
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 confidenceThis is a Missing Authorization vulnerability in the raratheme Construction Landing Page WordPress theme. The theme fails to properly verify user permissions before allowing access to certain functionality, allowing unauthorized users to perform actions they should not have access to due to incorrectly configured access control security levels.
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.
-
Verify the theme is installedNavigate to Appearance > Themes in WordPress admin panel and confirm 'raratheme Construction Landing Page' is listed as an active or installed theme.Affected if The theme is installed and active in WordPress.
-
Identify the theme versionAccess the theme directory via FTP or file manager, then open the style.css file in wp-content/themes/construction-landing-page/ and locate the 'Version:' header in the file comments.Affected if The installed version differs from any patched version the vendor may release.
-
Review theme PHP files for capability checksExamine key PHP files in the theme directory (such as functions.php, any admin-related PHP files, or AJAX handlers) and search for the presence of current_user_can() or similar authorization functions before sensitive operations.Affected if Sensitive functions or admin actions lack proper current_user_can() capability verification.
-
Check AJAX and admin action hooksSearch the theme PHP files for add_action calls tied to admin hooks (admin_init, wp_ajax_*) and verify each has a capability check (like current_user_can('manage_options')) before executing.Affected if AJAX endpoints or admin actions perform operations without verifying user permissions.
-
Audit nonce verificationSearch theme files for $_POST, $_GET, or $_REQUEST usage in admin contexts and verify that nonce verification (check_admin_referer or wp_verify_nonce) is present before processing those requests.Affected if Form submissions or URL parameters in admin areas lack nonce validation.
If the Construction Landing Page theme is installed and its version lacks the patched authorization fixes, and if admin-sensitive functions in the theme are missing capability and nonce checks, the environment is vulnerable to unauthorized actions.
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 dataThe theme developer should implement proper authorization checks (capability checks using current_user_can() and nonce verification) on all sensitive functions and admin actions. Users should update to a patched version once available or restrict admin access to trusted users until fixed.
- 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-32338 — 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-32338 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