CVE-2024-50449
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in RedefiningTheWeb PDF Generator Addon for Elementor Page Builder pdf-generator-addon-for-elementor-page-builder allows Stored XSS.This issue affects PDF Generator Addon for Elementor Page Builder: from n/a through <= 1.7.4.
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 confidenceA stored XSS vulnerability exists in PDF Generator Addon for Elementor Page Builder where user-supplied input is not properly sanitized before being embedded in generated PDFs or web pages. An attacker with contributor-level access or higher can inject malicious JavaScript that executes when other users view the PDF output.
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< 1.7.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if the vulnerable plugin is installedNavigate to WordPress admin > Plugins and look for 'Pdf Generator Addon For Elementor Page Builder' by Redefiningtheweb, or check the plugin filesystem for a folder named similarly under wp-content/plugins/Affected if The plugin is present in the WordPress installation
-
Check the installed versionIn WordPress admin > Plugins, click on the plugin to view details and compare the version number against the vulnerable range of versions before 1.7.5Affected if The installed version is lower than 1.7.5
-
Determine if PDF generation features are actively usedCheck if any pages or posts have been created using the Elementor PDF Generator widget or if any templates exist that generate PDFs, as the XSS only triggers when PDFs are actually generated and viewedAffected if PDF generation functionality has been used to create downloadable PDFs from user-edited content
-
Inspect Elementor content for user-supplied fieldsReview recent posts or pages created by contributor-level or higher users that use the PDF generator, looking for suspicious script tags or event handlers in text fields that would be included in PDF outputAffected if User-contributed content has been processed through the PDF generator without sanitization visible in the output
You are affected if the Redefiningtheweb Pdf Generator Addon for Elementor plugin is installed with a version below 1.7.5 and PDF generation has been used on content from users with contributor-level access or higher.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.7.5
Upgrade to version 1.7.5 or later which contains the security fix. Until then, restrict user permissions to the plugin and sanitize all user inputs before PDF rendering.
1.7.5
- Backup your WordPress site before making any changes
- Navigate to the WordPress admin dashboard
- Go to Plugins > Installed Plugins
- Find 'PDF Generator Addon for Elementor Page Builder' and check for update availability
- Update the plugin to version 1.7.5 or later
- Verify the update was successfully applied by checking the plugin version
- Test PDF generation functionality to ensure the plugin continues to work correctly after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2024-50449 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-50449 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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