dbcve.org
Post In Page For ElementorWordPress extension · Migaweb

CVE-2025-46225

MEDIUM · 5.4 CVSS v3.1 Published 2025-04-22
Fix available
A fix is available. Upgrade to 1.0.2 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Michael Post in page for Elementor allows DOM-Based XSS. This issue affects Post in page for Elementor: from n/a through 1.0.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

DOM-Based XSS vulnerability in the 'Post in page for Elementor' plugin allows attackers to inject malicious JavaScript through user-controlled input that gets dynamically inserted into the DOM without proper sanitization. The vulnerability affects versions up to and including 1.0.1 and stems from insecure handling of input during web page generation on the client side.

MitigationUpdate to the latest version of the plugin which should include proper input sanitization and output encoding. If no update is available, implement Content Security Policy (CSP) headers and review the plugin's JavaScript code to identify and fix the vulnerable sink where user input is inserted into the DOM.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Post In Page For ElementorWordPress extension
Affected:< 1.0.2

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Check plugin version
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Migaweb Post In Page For Elementor' or navigate to the plugin's settings page to find the version number. Compare against the affected range: versions below 1.0.2 are vulnerable.
    Affected if Plugin version is 1.0.1 or below
  2. Confirm plugin is active
    Verify the 'Post in page for Elementor' plugin is activated in WordPress under Plugins > Installed Plugins.
    Affected if Plugin is activated and being used on the site
  3. Identify pages using the plugin
    Review pages built with Elementor that use the 'Post in page' widget or shortcode provided by this plugin.
    Affected if The plugin's widget or shortcode is present on any page where end users can submit or control content
  4. Check for user-supplied input handling
    Inspect the page HTML and JavaScript to see if user-controlled data (such as post content, custom fields, or URL parameters) gets rendered via the plugin without server-side sanitization.
    Affected if The plugin renders user-supplied content directly into the DOM without escaping

A site is affected if the Migaweb Post In Page For Elementor plugin version is 1.0.1 or lower and the plugin is actively rendering user-controlled content on pages.

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
Upgrade available Upgrade to 1.0.2 or later
Fixed in 1.0.2
Interim mitigation

Update to the latest version of the plugin which should include proper input sanitization and output encoding. If no update is available, implement Content Security Policy (CSP) headers and review the plugin's JavaScript code to identify and fix the vulnerable sink where user input is inserted into the DOM.

Recommended fix High confidence

1.0.2

  1. Backup your WordPress site before making any changes
  2. Navigate to WordPress admin dashboard > Plugins > All Plugins
  3. Locate 'Post In Page For Elementor' in the plugins list
  4. Click 'Update Now' or manually update to version 1.0.2
  5. Verify the plugin shows version 1.0.2 after updating
  6. Clear any caching plugins or server-side caches

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

Fix this in Post In Page For Elementor Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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