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

CVE-2025-46514

HIGH · 7.1 CVSS v3.1 Published 2025-04-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
Cross-Site Request Forgery (CSRF) vulnerability in milat Milat jQuery Automatic Popup milat-jquery-automatic-popup allows Stored XSS.This issue affects Milat jQuery Automatic Popup: from n/a through <= 1.3.1.

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 · moderate confidence

This is a CSRF vulnerability in the Milat jQuery Automatic Popup plugin that allows attackers to inject Stored XSS payloads. By tricking an authenticated administrator into visiting a malicious site, attackers can execute Cross-Site Request Forgery attacks that inject persistent malicious scripts into the popup configuration, which then execute when other users view the affected content.

MitigationAdd CSRF tokens (nonces) to all admin forms and validate them server-side. Implement proper Origin/Referer header validation and use the plugin's existing security mechanisms to prevent unauthorized state 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
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

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 your plugins directory or plugin list for 'Milat jQuery Automatic Popup' or similar named popup plugin. In WordPress, this can be done via wp-admin/plugins.php or by inspecting /wp-content/plugins/ directory.
    Affected if The plugin is installed and active on the site
  2. Identify plugin version
    Locate the plugin's main PHP file (often named similar to milat-popup.php or within a 'milat' folder in /wp-content/plugins/) and check the Version header in the file header comment. Compare this version to any official vulnerable version listings if available.
    Affected if The installed version matches or falls within a known vulnerable version range for this CVE
  3. Inspect admin form CSRF protection
    Access the plugin's admin settings page (typically under Plugins or a dedicated Popup menu). View the page source or intercept the HTTP request when saving popup configuration. Check if forms include a nonce field (wpnonce, _wpnonce, or similar) or CSRF token.
    Affected if Forms lack nonce/CSRF tokens and the plugin is accessible to authenticated administrators
  4. Examine popup configuration for injected scripts
    Access the plugin's database entries (wp_options table with option_name containing 'milat' or 'popup') or the plugin's admin interface. Inspect the stored popup content/configuration for unexpected script tags, iframe elements, or javascript: URLs.
    Affected if Popup configuration contains unsanitized script tags or XSS payloads that were not intentionally added
  5. Verify admin session exposure risk
    Determine if administrators can be tricked into visiting external sites while authenticated (check for admin session cookies and whether the site implements proper Origin/Referer validation on admin actions).
    Affected if Admin actions can be triggered via cross-site requests without proper origin validation

A site is affected if the Milat jQuery Automatic Popup plugin is installed and its admin forms lack CSRF token protection, allowing stored XSS injection via crafted requests.

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

Add CSRF tokens (nonces) to all admin forms and validate them server-side. Implement proper Origin/Referer header validation and use the plugin's existing security mechanisms to prevent unauthorized state changes.

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