dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-3555

HIGH · 7.2 CVSS v3.1 Published 2024-06-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
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 Social Link Pages: link-in-bio landing pages for your social media profiles plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on the import_link_pages() function in all versions up to, and including, 1.6.9. This makes it possible for unauthenticated attackers to inject arbitrary pages and malicious web scripts.

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 Social Link Pages WordPress plugin has a missing capability check on the import_link_pages() function in versions up to 1.6.9. This allows unauthenticated attackers to call this function directly and inject arbitrary pages containing malicious web scripts into the site.

MitigationUpdate the Social Link Pages plugin to version 1.6.10 or later which includes the capability check fix. If immediate updating is not feasible, consider temporarily disabling the plugin or deploying WAF rules to block unauthorized access to the vulnerable function.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 Social Link Pages plugin
    Check the wp-content/plugins/ directory for a folder named 'social-link-pages' or similar. Alternatively, log into WordPress admin and navigate to Plugins to find 'Social Link Pages' in the list of installed plugins.
    Affected if The plugin folder or entry is not found in the plugins directory or admin list.
  2. Identify the installed version
    Open the main plugin file (usually social-link-pages.php or similar in the plugin folder) and look for the version comment at the top, such as 'Version: 1.6.9'. Alternatively, in WordPress admin, go to Plugins and click on the plugin to view its details where the version is displayed.
    Affected if The version cannot be determined or the plugin is not present.
  3. Compare version against affected range
    If the version is found, compare it numerically against 1.6.9. Versions 1.6.9 and below are affected; version 1.6.10 and later are fixed.
    Affected if The installed version is 1.6.9 or any version number lower than 1.6.9 (e.g., 1.6.8, 1.6.0, 0.1).
  4. Verify the vulnerable function exists
    Check the plugin source code for the import_link_pages() function. If the file containing this function is present and the plugin is active, the vulnerability is accessible to unauthenticated attackers.
    Affected if The import_link_pages() function exists in the plugin files and the plugin is active on the site.

You are affected if the Social Link Pages plugin is installed and active with version 1.6.9 or lower, because the missing capability check allows unauthenticated access to the import_link_pages() function.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Social Link Pages plugin to version 1.6.10 or later which includes the capability check fix. If immediate updating is not feasible, consider temporarily disabling the plugin or deploying WAF rules to block unauthorized access to the vulnerable function.

Recommended fix Moderate confidence

Social Link Pages plugin version 1.7.0 or later

  1. Update the Social Link Pages plugin to version 1.7.0 or later
  2. Verify the update was successful by checking the plugin version in WordPress admin under Plugins > Installed Plugins
  3. Confirm that the import_link_pages() function now includes proper capability checks (e.g., current_user_can('manage_options') or similar)
  4. Test that legitimate administrative functions still work correctly after the update
  5. Review any newly created or modified pages for unexpected content that may have been injected during any prior exploitation

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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