All Bootstrap BlocksWordPress extension · Areoi

CVE-2023-35047

MEDIUM · 6.5 CVSS v3.1 Published 2023-07-11
Fix available
A fix is available. Upgrade to after 1.3.6 or later.
See remediation →
72/100
Remediation priority · Elevated
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 AREOI All Bootstrap Blocks plugin <= 1.3.6 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

Cross-Site Request Forgery (CSRF) vulnerability in the AREOI All Bootstrap Blocks WordPress plugin versions 1.3.6 and below. Attackers can craft malicious requests that trick authenticated administrators into performing unintended actions (such as modifying plugin settings or content) without their knowledge.

MitigationUpdate the plugin to a version beyond 1.3.6 that addresses this vulnerability. If no update is available, implement WordPress nonce verification for all form submissions and state-changing operations within the plugin.

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
All Bootstrap BlocksWordPress extension
Affected:<= 1.3.6

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
None
Integrity
High
Availability
None

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

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

  1. Locate the plugin installation directory
    Check the WordPress plugins folder at wp-content/plugins/ for a folder named 'areoi-all-bootstrap-blocks' or similar variation of 'areoi'
    Affected if The plugin directory exists on the server
  2. Identify the installed plugin version
    Open the main plugin PHP file (typically areoi.php or similar in the plugin folder) and locate the 'Version' field in the plugin header comment at the top of the file
    Affected if The reported version number is 1.3.6 or lower
  3. Verify the plugin is active
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or query the WordPress database wp_options table for the option_name 'active_plugins'
    Affected if The plugin appears in the list of active plugins
  4. Confirm vulnerability applicability
    Compare your installed version against the affected range: any version <= 1.3.6 is within the vulnerable range specified in the CVE
    Affected if Your installed version is 1.3.6 or any earlier version number

You are affected if the AREOI All Bootstrap Blocks plugin is installed, active, and running at version 1.3.6 or lower.

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.

From vendor data
Upgrade available Upgrade to a release after 1.3.6
Interim mitigation

Update the plugin to a version beyond 1.3.6 that addresses this vulnerability. If no update is available, implement WordPress nonce verification for all form submissions and state-changing operations within the plugin.

Fix this in All Bootstrap Blocks Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
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,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-35047 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-35047 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