dbcve.org
Sync Post With Other SiteWordPress extension · Syncpostwithothersite

CVE-2024-32082

MEDIUM · 6.1 CVSS v3.1 Published 2024-04-15
Fix available
A fix is available. Upgrade to after 1.8 or later.
See remediation →
68/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 Kamlesh Parmar Sync Post With Other Site sync-post-with-other-site allows Cross Site Request Forgery.This issue affects Sync Post With Other Site: from n/a through <= 1.9.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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in the WordPress plugin 'Sync Post With Other Site' versions 1.9.1 and below. The plugin fails to properly validate anti-CSRF tokens on state-changing operations, allowing authenticated administrators to be tricked into triggering unwanted post synchronization actions to external sites via maliciously crafted requests.

MitigationImplement WordPress nonces (wp_create_nonce/wp_verify_nonce) on all forms and AJAX actions that perform synchronization, and verify the request origin via the Origin or Referer header before processing any state-changing requests.

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
Sync Post With Other SiteWordPress extension
Affected:<= 1.8

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

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

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

  1. Identify plugin version
    Locate the plugin directory 'syncpostwithothersite' or 'sync-post-with-other-site' in wp-content/plugins and read the main plugin file header to find the Version field
    Affected if Version listed is 1.9.1 or below, or the Version field is missing/invalid (indicating an unpatched release)
  2. Confirm plugin is active
    Check WordPress admin under Plugins > Installed Plugins, or query the wp_options table for 'active_plugins' option to see if the plugin is enabled
    Affected if Plugin shows as active and the version check above is true
  3. Examine sync AJAX handlers for nonce validation
    In the plugin's main PHP file, locate functions handling AJAX requests related to synchronization (look for wp_ajax_ hooks). Check if these functions call wp_verify_nonce() or wp_create_nonce() before processing the request
    Affected if AJAX handlers for sync actions exist but do not contain nonce verification calls, or the nonce checks are commented out/missing
  4. Inspect sync forms for nonce fields
    Search plugin files for form outputs that trigger synchronization (look for '<form' tags and sync-related action URLs). Verify that each form includes a nonce field using wp_nonce_field() or similar
    Affected if Forms that trigger state-changing sync operations exist but lack nonce input fields, or the nonce fields are not being sent with the request
  5. Check referer/origin validation on sync requests
    Examine the synchronization processing code to see if it validates the request origin via check_admin_referer(), $_SERVER['HTTP_ORIGIN'], or $_SERVER['HTTP_REFERER'] before executing sync actions
    Affected if No origin/referer validation is performed on synchronization requests, allowing requests from any source

You are affected if the plugin version is 1.9.1 or below AND the synchronization functionality lacks proper nonce validation on AJAX handlers or forms.

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.8
Interim mitigation

Implement WordPress nonces (wp_create_nonce/wp_verify_nonce) on all forms and AJAX actions that perform synchronization, and verify the request origin via the Origin or Referer header before processing any state-changing requests.

Fix this in Sync Post With Other Site Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,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 $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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