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

CVE-2025-7668

MEDIUM · 6.1 CVSS v3.1 Published 2025-08-16
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 Linux Promotional Plugin plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.4. This is due to missing or incorrect nonce validation on the 'inux-promotional-plugin.php' page. 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 Linux Promotional Plugin for WordPress (versions up to 1.4) lacks proper nonce validation on its settings page (linux-promotional-plugin.php). This allows unauthenticated attackers to forge administrative requests by tricking a logged-in admin into clicking a malicious link, enabling settings modification and stored script injection.

MitigationUpdate the plugin to the latest version which implements proper nonce validation for all state-changing operations. Until then, warn administrators not to click untrusted links while logged in.

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 plugin installation
    Check if the Linux Promotional Plugin directory exists in wp-content/plugins/ (typically named linux-promotional-plugin or similar)
    Affected if The plugin directory exists in the WordPress plugins folder
  2. Identify installed version
    Open the main plugin file (linux-promotional-plugin.php) and look for the version header comment (e.g., 'Version: X.X') or check the plugin's readme.txt for the Version field
    Affected if The reported version is 1.4 or below (including any version like 1.0, 1.1, 1.2, 1.3, 1.4)
  3. Verify plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and check if Linux Promotional Plugin is activated
    Affected if The plugin shows as Active in the WordPress plugins list
  4. Check settings page accessibility
    Navigate to the plugin's settings page (usually under Settings > Linux Promotional or a dedicated admin menu item added by the plugin)
    Affected if The settings page loads and accepts input without requiring a fresh page load or displaying validation errors
  5. Inspect for nonce tokens in settings form
    View the page source of the plugin settings page and search for a hidden input with name 'wpnonce' or similar security token, or check if the form tag includes a nonce field
    Affected if No nonce token (wpnonce, _wpnonce, etc.) is found in the HTML source of the plugin's settings form

A user is affected if the Linux Promotional Plugin version 1.4 or below is installed and active on their WordPress site, and the settings page lacks proper nonce validation.

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 plugin to the latest version which implements proper nonce validation for all state-changing operations. Until then, warn administrators not to click untrusted links while logged in.

Recommended fix Moderate confidence

Version higher than 1.4 (check WordPress plugin repository for latest patched version)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Linux Promotional Plugin' in the list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Verify the plugin was updated to a version higher than 1.4
  6. 6. Confirm the nonce validation fix is present by reviewing plugin changelog or code if needed

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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