dbcve.org
Pearl Header BuilderWordPress extension · Stylemixthemes

CVE-2022-38356

HIGH · 8.8 CVSS v3.1 Published 2023-05-25
Fix available
A fix is available. Upgrade to after 1.3.4 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Cross-Site Request Forgery (CSRF) vulnerability in StylemixThemes WordPress Header Builder Plugin – Pearl plugin <= 1.3.4 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 confidence

This is a Cross-Site Request Forgery (CSRF) vulnerability in the Pearl WordPress Header Builder plugin by StylemixThemes affecting versions 1.3.4 and earlier. CSRF attacks exploit authenticated sessions by tricking users into unknowingly submitting malicious requests to vulnerable endpoints that lack proper token validation.

MitigationUpgrade to the latest version of the Pearl plugin when available. If no patched version exists, implement WordPress nonces on all state-changing form actions and validate Origin/Referer headers to prevent CSRF exploitation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Pearl Header BuilderWordPress extension
Affected:<= 1.3.4

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Pearl Header Builder plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Pearl Header Builder' by StylemixThemes, or check the wp-content/plugins directory for the pearl-header-builder folder
    Affected if The plugin is present in the WordPress installation
  2. Check installed plugin version
    In WordPress admin > Plugins > Installed Plugins, click on the plugin details for Pearl Header Builder and view the Version number, or read the main plugin file header in wp-content/plugins/pearl-header-builder/
    Affected if The version number is 1.3.4 or lower
  3. Identify plugin admin pages and form actions
    Scan the plugin files in wp-content/plugins/pearl-header-builder/ for PHP files containing form handlers, admin_init hooks, or AJAX actions that modify plugin settings or header configurations
    Affected if Form handling code exists without wp_nonce_field() or check_admin_referer() calls
  4. Inspect AJAX endpoints for nonce validation
    Search plugin PHP files for add_action('wp_ajax_') calls and verify if each handler includes nonce verification using check_ajax_referer() or wp_verify_nonce()
    Affected if AJAX actions exist that process requests without nonce validation
  5. Review plugin settings pages
    Access the Pearl Header Builder settings in WordPress admin (usually under Appearance > Header Builder or similar) and inspect any forms that save or update configurations
    Affected if Save/submit forms are present without CSRF token fields or with missing token validation in their handler code

The environment is affected if the Pearl Header Builder plugin version 1.3.4 or lower is installed and contains form or AJAX actions that lack WordPress nonce verification.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.3.4
Interim mitigation

Upgrade to the latest version of the Pearl plugin when available. If no patched version exists, implement WordPress nonces on all state-changing form actions and validate Origin/Referer headers to prevent CSRF exploitation.

Recommended fix Moderate confidence

Latest available version (higher than 1.3.4)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find the 'Pearl Header Builder' plugin by StylemixThemes
  4. Check if an update is available and update to the latest version (version higher than 1.3.4)
  5. Alternatively, download the latest version from the WordPress Plugin Directory or StylemixThemes website and reinstall

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pearl Header Builder Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-38356 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-38356 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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