dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-12542

HIGH · 8.6 CVSS v3.1 Published 2025-01-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
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 linkID plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check when including the 'phpinfo' function in all versions up to, and including, 0.1.2. This makes it possible for unauthenticated attackers to read configuration settings and predefined variables on the site's server. The plugin does not need to be activated for the vulnerability to be exploited.

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 linkID WordPress plugin has a missing capability check that allows unauthenticated users to access the phpinfo() function. This exposes server configuration settings, environment variables, and other sensitive predefined variables. The vulnerability is exploitable even when the plugin is not activated.

MitigationRemove or disable the linkID plugin entirely. If an updated version beyond 0.1.2 is available from the vendor, update to the patched version.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/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. Locate linkID plugin files
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'linkID' or similar. Even if the plugin is not activated, its files may still be present on the server.
    Affected if The linkID plugin folder exists in the WordPress plugins directory.
  2. Determine plugin version
    Open the main plugin file (usually linkID.php or index.php inside the linkID folder) and read the 'Version' field from the plugin header comment. Compare this version number to the affected range (0.1.2 and below).
    Affected if The installed version is 0.1.2 or lower.
  3. Verify plugin is not activated but still present
    In WordPress admin, go to Plugins > Installed Plugins and confirm whether linkID is deactivated. The vulnerability applies even in this deactivated state as long as plugin files remain on the server.
    Affected if The plugin files exist but the plugin shows as deactivated or is not listed in active plugins.
  4. Check for public phpinfo() exposure
    Inspect web server access logs or attempt a request to common plugin endpoints (such as /wp-content/plugins/linkID/[vulnerable-file].php?action=phpinfo or similar patterns). Look for any URL that triggers phpinfo() output.
    Affected if Requests to the plugin directory return phpinfo() output or the server configuration is exposed through the plugin endpoint.
  5. Review server configuration for exposed PHP variables
    If phpinfo() is accessible, verify whether sensitive variables such as environment variables (env), $_SERVER superglobals, or other predefined PHP variables are visible in the output.
    Affected if The phpinfo() output is publicly accessible and reveals environment variables, server configuration, or other sensitive predefined variables.

The environment is affected if the linkID plugin files exist on the server (even when deactivated) and the version is 0.1.2 or lower, allowing unauthenticated access to phpinfo() which exposes server configuration and sensitive variables.

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

Remove or disable the linkID plugin entirely. If an updated version beyond 0.1.2 is available from the vendor, update to the patched version.

Have this fixed 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 help mitigating

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-12542 — 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-12542 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