dbcve.org
Actionwear Products SyncWordPress extension · Marcoingraiti

CVE-2024-13535

MEDIUM · 5.3 CVSS v3.1 Published 2025-02-18
Fix available
A fix is available. Upgrade to 2.3.3 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
The Actionwear products sync plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 2.3.2. This is due the composer-setup.php file being publicly accessible with 'display_errors' set to true. This makes it possible for unauthenticated attackers to retrieve the full path of the web application, which can be used to aid other attacks. The information displayed is not useful on its own, and requires another vulnerability to be present for damage to an affected website.

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 · high confidence

The Actionwear products sync WordPress plugin up to version 2.3.2 contains a publicly accessible composer-setup.php file with PHP display_errors enabled. This configuration allows unauthenticated attackers to trigger error messages that expose the full server filesystem path, information that can be leveraged to aid exploitation of other vulnerabilities.

MitigationRemove or restrict public access to the composer-setup.php file, and disable display_errors in php.ini or via ini_set() to prevent full path disclosure.

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
Actionwear Products SyncWordPress extension
Affected:< 2.3.3

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Identify installed plugin version
    Locate the Actionwear Products Sync plugin in your WordPress wp-content/plugins directory and check the main plugin file (usually plugin-name.php or readme.txt) for the Version header, or query it via WP-CLI: wp plugin list --search='actionwear' --format=json
    Affected if The installed version is 2.3.2 or lower (anything below 2.3.3)
  2. Check for composer-setup.php file existence
    List the files in the plugin directory (wp-content/plugins/actionwear-products-sync or similar naming) and look for a file named composer-setup.php
    Affected if The composer-setup.php file exists in the plugin directory
  3. Verify web accessibility of composer-setup.php
    Attempt to access the file via HTTP request: curl -I https://yourdomain.com/wp-content/plugins/[plugin-folder]/composer-setup.php (adjust path based on actual plugin folder name)
    Affected if The file returns an HTTP 200 response and is accessible without authentication
  4. Check PHP display_errors configuration
    Check your PHP configuration (php.ini) or run: php -i | grep display_errors OR create a PHP info page to verify the display_errors setting is On
    Affected if PHP display_errors is set to On (enabled)

You are affected if the plugin version is below 2.3.3 AND the composer-setup.php file exists and is web-accessible AND PHP display_errors is enabled, as this combination allows unauthenticated path disclosure.

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 2.3.3 or later
Fixed in 2.3.3
Interim mitigation

Remove or restrict public access to the composer-setup.php file, and disable display_errors in php.ini or via ini_set() to prevent full path disclosure.

Recommended fix High confidence

2.3.3

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the 'Actionwear Products Sync' plugin
  4. 4. Click 'Update now' if an update is available, or manually update to version 2.3.3
  5. 5. Verify the update was successful and the plugin is running version 2.3.3 or higher

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

Fix this in Actionwear Products Sync Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-13535 — 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-2024-13535 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