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

CVE-2025-58268

HIGH · 7.1 CVSS v3.1 Published 2025-09-22
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 WPMK WPMK PDF Generator wpmk-pdf-generator allows Stored XSS.This issue affects WPMK PDF Generator: 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

A CSRF vulnerability in the WPMK PDF Generator WordPress plugin allows attackers to inject malicious scripts through forged requests, resulting in Stored XSS. When an authenticated administrator unknowingly submits a crafted request, the XSS payload is persisted in the database and executes when other users view the affected content.

MitigationUpdate to a patched version of WPMK PDF Generator; if unavailable, disable the plugin. Implement anti-CSRF tokens and proper input sanitization/validation for all user-supplied data.

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. Verify WPMK PDF Generator plugin is installed
    Log into WordPress admin panel, navigate to Plugins > Installed Plugins, and search for 'WPMK PDF Generator' or check the plugins directory via FTP at /wp-content/plugins/
    Affected if the plugin is present and active in the WordPress installation
  2. Identify installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find WPMK PDF Generator, and note the version number displayed under the plugin name
    Affected if version cannot be determined or is unknown
  3. Check for stored XSS in plugin-generated content
    Access the WordPress database (via phpMyAdmin or command line) and query posts/pages for suspicious script tags or event handlers in content fields, particularly those associated with PDF generation functionality: SELECT * FROM wp_posts WHERE post_content LIKE '%<script%' OR post_content LIKE '%onerror=%' OR post_content LIKE '%onload=%'
    Affected if any stored XSS payloads are found in the database related to PDF content
  4. Inspect plugin settings for unsanitized input storage
    Check the wp_postmeta table for meta keys related to WPMK PDF Generator and examine their values for unescaped HTML or JavaScript: SELECT * FROM wp_postmeta WHERE meta_key LIKE '%wpmk%'
    Affected if plugin meta entries contain raw HTML/script content without sanitization
  5. Verify admin session compromise indicators
    Review WordPress access logs or security logs for POST requests to wp-admin/admin-ajax.php or plugin admin pages containing suspicious payloads with script tags, especially from admin sessions
    Affected if anomalous requests with XSS payloads were made from admin accounts

Users are affected if the WPMK PDF Generator plugin is installed and either the version is unpatched or stored XSS payloads are present in the database.

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

Update to a patched version of WPMK PDF Generator; if unavailable, disable the plugin. Implement anti-CSRF tokens and proper input sanitization/validation for all user-supplied data.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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