dbcve.org
Digital Publications By SupsysticWordPress extension · Supsystic

CVE-2023-5756

HIGH · 8.8 CVSS v3.1 Published 2023-12-09
Fix available
A fix is available. Upgrade to after 1.7.6 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
The Digital Publications by Supsystic plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.7.6. This is due to missing or incorrect nonce validation on the AJAX action handler. This makes it possible for unauthenticated attackers to execute AJAX actions via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 Digital Publications by Supsystic WordPress plugin lacks proper nonce validation in its AJAX action handlers, allowing unauthenticated attackers to craft forged requests that execute AJAX actions. Successful exploitation requires social engineering a site administrator into clicking a malicious link, leveraging the trusted context of an authenticated admin session.

MitigationUpdate the plugin to version 1.7.7 or later, which should include proper nonce validation for AJAX handlers. Until then, exercise caution with links clicked while logged into the WordPress admin.

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
Digital Publications By SupsysticWordPress extension
Affected:<= 1.7.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
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. Check the installed plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins > Digital Publications by Supsystic and look at the version number displayed
    Affected if The version listed is 1.7.6 or lower
  2. Verify the plugin is active
    In the WordPress admin plugins list, confirm that Digital Publications by Supsystic shows as 'Active'
    Affected if The plugin is active and the version is 1.7.6 or below - the vulnerable AJAX handlers are reachable
  3. Identify accessible AJAX endpoints
    Check the plugin directory (wp-content/plugins/digital-publications-by-supsystic) for PHP files containing 'wp_ajax_' or 'add_action' calls that register AJAX handlers
    Affected if AJAX action handlers are registered and the plugin version is 1.7.6 or below, meaning they may lack proper nonce validation as described in the CVE

A user is affected if they have Digital Publications by Supsystic plugin installed, active, and running version 1.7.6 or lower, as this version lacks proper nonce validation in its AJAX handlers.

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

Update the plugin to version 1.7.7 or later, which should include proper nonce validation for AJAX handlers. Until then, exercise caution with links clicked while logged into the WordPress admin.

Recommended fix Moderate confidence

Latest available version of Digital Publications By Supsystic (version > 1.7.6)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Digital Publications By Supsystic' in the plugin list
  4. If an update is available, click 'Update Now' to install the latest version
  5. Alternatively, navigate to Dashboard > Updates and select the plugin to update
  6. After updating, verify the version number reflects the latest available release (should be > 1.7.6)
  7. Clear any caching plugins if present and test that the plugin functionality works correctly
Caveat Minor: Verify custom configurations or publication templates remain functional after upgrade

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

Fix this in Digital Publications By Supsystic 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-2023-5756 — 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-2023-5756 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