dbcve.org
Pz LinkcardWordPress extension · Popozure

CVE-2023-47790

MEDIUM · 6.1 CVSS v3.1 Published 2023-11-23
Fix available
A fix is available. Upgrade to after 2.4.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) leading to Cross-Site Scripting (XSS) vulnerability in Poporon Pz-LinkCard plugin <= 2.4.8 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

A CSRF-to-XSS chain in the Pz-LinkCard WordPress plugin versions 2.4.8 and below allows an attacker to trick an authenticated administrator into performing unintended actions that inject malicious scripts into the site.

MitigationUpdate the Pz-LinkCard plugin to a version newer than 2.4.8. If no update is available, disable the plugin until a patch is released.

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
Pz LinkcardWordPress extension
Affected:<= 2.4.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. Locate the Pz-LinkCard plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'pz-linkcard' or similar variant containing 'linkcard' in the name
    Affected if The plugin folder exists in the plugins directory
  2. Identify the installed plugin version
    Open the main plugin PHP file and look for the version comment header, or access the WordPress admin Plugins page and locate Pz-LinkCard in the list
    Affected if The version displayed is 2.4.8 or lower, or no version number is shown (meaning an old installation)
  3. Verify the plugin is active
    In the WordPress admin, go to Plugins > Installed Plugins and confirm Pz-LinkCard shows as 'Active'
    Affected if The plugin status is Active
  4. Check for admin session vulnerability
    Review whether the WordPress site has admin users who may be susceptible to social engineering attacks (CSRF requires tricking an authenticated administrator)
    Affected if Authenticated administrators exist who could be coerced into clicking malicious links in the admin dashboard
  5. Inspect plugin admin pages for unprotected forms
    Access the plugin settings page (usually under Settings > Pz-LinkCard) and examine if the form submissions lack CSRF tokens or sanitization
    Affected if The plugin admin forms do not include security tokens or have obvious missing nonce validations

The environment is affected if Pz-LinkCard version 2.4.8 or lower is installed and active, exposing admin users to CSRF-to-XSS attacks.

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

Update the Pz-LinkCard plugin to a version newer than 2.4.8. If no update is available, disable the plugin until a patch is released.

Recommended fix Moderate confidence

2.4.9 or later (check WordPress plugin repository for latest stable release)

  1. Check current plugin version in WordPress admin under Plugins > Installed Plugins
  2. Navigate to Plugins > Add New > Upload Plugin or update directly from the Plugins page if an update is available
  3. If no update is available through WordPress, manually download the latest version from the official WordPress plugin repository
  4. Backup the site before updating
  5. Activate the updated plugin version

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

Fix this in Pz Linkcard Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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