Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-12404

MEDIUM · 6.1 CVSS v3.1 Published 2025-11-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
The Like-it plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.2. This is due to missing or incorrect nonce validation on the likeit_conf() function. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts 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 Like-it WordPress plugin lacks proper nonce validation in the likeit_conf() function, allowing unauthenticated attackers to forge requests that modify plugin settings. Successful exploitation enables injection of malicious web scripts through the updated settings, with the attack requiring social engineering to trick a site administrator into clicking a malicious link.

MitigationUpdate to a patched version of the Like-it plugin if available; otherwise, disable the plugin until a fix can be applied. Review existing plugin settings for any unauthorized changes.

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
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. Confirm the Like-it plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Like-it', or inspect the wp-content/plugins directory for a like-it folder
    Affected if The plugin is present in the WordPress installation
  2. Determine the installed plugin version
    In WordPress admin, click on the Like-it plugin to view its details, or open the main plugin PHP file and look for the 'Version' header in the plugin comments
    Affected if The installed version is older than any patched version released for CVE-2025-12404
  3. Inspect the likeit_conf() function for nonce validation
    Locate the main plugin PHP file and search for the function 'likeit_conf'. Examine the function code to see if it calls wp_verify_nonce() or check_admin_referer() before processing settings changes
    Affected if The function exists but does not perform nonce verification on the settings update request
  4. Verify plugin settings have not been tampered with
    In WordPress admin, navigate to the Like-it plugin settings page and review all configuration values for unexpected or malicious content, particularly fields that could store web scripts
    Affected if Any settings contain unexpected JavaScript, HTML, or URLs pointing to suspicious domains
  5. Review database for unauthorized setting modifications
    Query the wp_options table for option_name values related to the plugin (like 'likeit_settings' or similar) and examine the option_value for injected scripts or altered configuration
    Affected if Database settings contain encoded or plaintext malicious scripts, or show recent modifications you did not make

If the Like-it plugin is installed and the likeit_conf() function lacks nonce validation, the environment is vulnerable to CVE-2025-12404 and settings may have been compromised.

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

Update to a patched version of the Like-it plugin if available; otherwise, disable the plugin until a fix can be applied. Review existing plugin settings for any unauthorized changes.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12404 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2025-12404 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