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

CVE-2025-12400

MEDIUM · 6.1 CVSS v3.1 Published 2025-11-04
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 LMB^Box Smileys plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.2. This is due to missing or incorrect nonce validation on the manage_page() 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 LMB^Box Smileys plugin for WordPress versions up to 3.2 lacks proper nonce validation in its manage_page() function, allowing unauthenticated attackers to forge administrative requests. This CSRF vulnerability enables attackers to modify plugin settings and potentially inject malicious scripts by tricking administrators into clicking crafted links.

MitigationSince the plugin appears unmaintained (no patch available for 3.2), replace it with a actively maintained smileys/emoticons plugin or remove it entirely; alternatively, apply custom nonce validation patches if plugin functionality is critical.

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. Locate the LMB^Box Smileys plugin
    In your WordPress installation, navigate to wp-content/plugins/ and look for a folder named 'lmb-box-smileys', 'lmbbox-smileys', or similar variants containing 'lmb' and 'smileys'
    Affected if The plugin directory exists in the plugins folder
  2. Determine the installed version
    Open the main plugin PHP file (usually index.php or lmb-box-smileys.php) and look for a version comment or header: 'Version: x.x.x' or 'Version: x.x'
    Affected if The version listed is 3.2 or any lower version number (e.g., 3.1, 3.0, 2.x)
  3. Verify the vulnerable function exists
    In the plugin directory, open the file containing manage_page() function (often admin.php or the main plugin file); search for 'function manage_page'
    Affected if The manage_page() function is present in the plugin code
  4. Check for nonce validation in manage_page
    Within the manage_page() function, look for 'wp_verify_nonce', 'check_admin_referer', or 'nonce' verification calls; also search for 'isset($_POST["nonce"])' or similar nonce field checks
    Affected if No nonce verification (wp_verify_nonce, check_admin_referer, or nonce_field) is found anywhere inside the manage_page() function

If the LMB^Box Smileys plugin is installed with version 3.2 or lower AND the manage_page() function lacks nonce validation checks, the environment is affected by this CSRF vulnerability.

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

Since the plugin appears unmaintained (no patch available for 3.2), replace it with a actively maintained smileys/emoticons plugin or remove it entirely; alternatively, apply custom nonce validation patches if plugin functionality is critical.

Recommended fix Moderate confidence

Version 3.3 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the LMB^Box Smileys plugin
  4. 4. Check if an update to version 3.3 or later is available
  5. 5. If an update is available, click 'Update Now' to install the fixed version
  6. 6. If no update is shown, manually download version 3.3 or later from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  7. 7. After updating, verify the plugin is functioning correctly

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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