CVE-2025-32502
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in lemmentwickler ePaper Lister for Yumpu magazine-lister-for-yumpu allows Stored XSS.This issue affects ePaper Lister for Yumpu: from n/a through <= 1.4.0.
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 CSRF vulnerability in the ePaper Lister for Yumpu WordPress plugin (versions up to 1.4.0) allows authenticated attackers to inject malicious JavaScript code (Stored XSS) by tricking administrators into submitting crafted requests. The lack of anti-CSRF tokens on state-changing endpoints enables attackers to silently inject malicious scripts that execute when other users view affected content.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify ePaper Lister for Yumpu plugin is installedLog into WordPress admin panel, navigate to Plugins > Installed Plugins, and look for 'ePaper Lister for Yumpu' in the list. Alternatively, check the wp-content/plugins directory for a folder named 'yumpu-epaper-lister' or similar.Affected if The plugin appears in the installed plugins list, regardless of activation status
-
Determine installed plugin versionIn the WordPress admin plugins list, click on the plugin to view its details, or inspect the main plugin PHP file (usually in wp-content/plugins/[plugin-folder]/index.php or similar) and look for the 'Version:' header in the plugin comment block.Affected if The version number displayed is 1.4.0 or lower
-
Check if admin actions are protected with noncesAccess the WordPress site via FTP or file manager, locate the main plugin PHP file, and search for functions handling form submissions or state-changing actions (such as save, update, add, delete). Look forwp_nonce_field, wp_verify_nonce, or check_admin_referer calls near those action handlers.Affected if No nonce verification (wp_nonce_field, wp_verify_nonce, check_admin_referer) is found in the code handling admin form submissions or state-changing operations
-
Inspect plugin-stored data for malicious scriptsCheck WordPress database tables (likely wp_options or wp_postmeta) for any saved ePaper Lister data that may contain script tags, iframe tags, or javascript: URIs. Use phpMyAdmin or run: SELECT * FROM wp_options WHERE option_name LIKE '%yumpu%';Affected if Stored data contains suspicious payloads such as <script>, <iframe, or javascript: URIs that were not intentionally added by the administrator
The environment is affected if the ePaper Lister for Yumpu plugin is installed with version 1.4.0 or lower and lacks nonce/CSRF protection on its admin action endpoints.
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.
From vendor dataUpgrade to version 1.4.1 or later which should include CSRF token validation. Until then, consider disabling the plugin or implementing web application firewall rules to block malicious requests.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32502 — 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-2025-32502 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