CVE-2025-49346
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 peterwsterling Simple Archive Generator simple-archive-generator allows Stored XSS.This issue affects Simple Archive Generator: from n/a through <= 5.2.
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 confidenceCSRF vulnerability in the Simple Archive Generator WordPress plugin allows authenticated attackers to inject malicious JavaScript through crafted form submissions. The lack of proper nonce verification on admin actions enables attackers to trick administrators into unknowingly executing stored XSS payloads that persist in the archive output.
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 Simple Archive Generator plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Simple Archive Generator' in the list. Note whether it is active or inactive.Affected if The plugin is installed and active
-
Identify installed plugin versionClick 'View details' on the Simple Archive Generator plugin in the WordPress plugins list, or check the plugin's main PHP file header for the 'Version' comment.Affected if Version cannot be determined or is prior to any patched release (the plugin lacks nonce verification in admin forms)
-
Inspect admin form submissions for nonce fieldsView page source of any admin page generated by Simple Archive Generator (typically in Settings or Tools menu). Look for form elements containing '_wpnonce' or 'nonce' fields.Affected if No nonce field is present in admin action forms, or the nonce is not validated server-side when the form is submitted
-
Check AJAX requests for nonce verificationUse browser developer tools Network tab to monitor AJAX requests made by the plugin. Examine the request parameters for 'nonce' or '_wpnonce' values.Affected if AJAX requests lack nonce parameters or do not verify nonce server-side
A user is affected if the Simple Archive Generator plugin is active and admin forms/AJAX requests lack proper WordPress nonce verification, allowing CSRF-driven stored XSS injection.
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 dataImplement WordPress nonces on all form submissions and AJAX requests, add SameSite cookie attributes, and validate request referers to prevent CSRF exploitation.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49346 — 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-49346 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