dbcve.org
Css Js Manager\, Async Javascript\, Defer Render Blocking Css Supports WoocommerceWordPress extension · Piwebsolution

CVE-2022-47154

HIGH · 8.8 CVSS v3.1 Published 2023-03-14
Fix available
A fix is available. Upgrade to after 2.4.49 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 Pi Websolution CSS JS Manager, Async JavaScript, Defer Render Blocking CSS supports WooCommerce plugin <= 2.4.49 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 Pi Websolution CSS JS Manager, Async JavaScript, Defer Render Blocking CSS WooCommerce plugin versions 2.4.49 and below allows attackers to trick authenticated administrators into performing unintended actions by forcing their browser to send malicious requests.

MitigationUpdate to a version newer than 2.4.49 or implement anti-CSRF tokens (nonces) on all form submissions and AJAX endpoints 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
Css Js Manager\, Async Javascript\, Defer Render Blocking Css Supports WoocommerceWordPress extension
Affected:<= 2.4.49

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. Identify the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Piwebsolution Css Js Manager, Async Javascript, Defer Render Blocking Css Supports Woocommerce' - the version number is displayed below the plugin name. Alternatively, check the main plugin PHP file (usually named like class-css-js-manager.php or similar in wp-content/plugins/css-js-manager/) for the 'Version' header in the plugin comment block.
    Affected if The displayed version is 2.4.49 or lower.
  2. Confirm the plugin is active
    Verify the plugin is currently activated on the WordPress site by checking the Plugins page in the WordPress admin dashboard - look for a 'Active' status indicator next to the plugin.
    Affected if The plugin is active and the version is 2.4.49 or below.
  3. Inspect plugin PHP files for missing nonce verification
    Using a file manager or code editor, examine the main plugin PHP files in wp-content/plugins/css-js-manager/ (or similar path). Search for form submission handlers and AJAX action hooks (add_action('wp_ajax_...')). Look for the absence of 'check_ajax_referer' or 'wp_verify_nonce' function calls before processing requests.
    Affected if Form handlers or AJAX endpoints do not contain nonce verification calls, meaning the plugin is vulnerable to CSRF attacks.

A user is affected if the Piwebsolution CSS JS Manager plugin is active at version 2.4.49 or below and the plugin's form submissions and AJAX endpoints lack 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 2.4.49
Interim mitigation

Update to a version newer than 2.4.49 or implement anti-CSRF tokens (nonces) on all form submissions and AJAX endpoints within the plugin.

Recommended fix Moderate confidence

Latest available version (2.4.50 or higher) from the WordPress Plugin Directory or the vendor

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate 'CSS JS Manager', 'Async JavaScript', or 'Defer Render Blocking CSS supports WooCommerce' (the plugin may be listed under 'Pi Websolution'
  4. 4. Check if an update is available
  5. 5. If an update is available, click 'Update Now' to install the latest version
  6. 6. Verify the update was successful and test the site functionality

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

Fix this in Css Js Manager\, Async Javascript\, Defer Render Blocking Css Supports Woocommerce 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-47154 — 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-47154 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