CVE-2025-49345
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 mg12 WP-EasyArchives wp-easyarchives allows Stored XSS.This issue affects WP-EasyArchives: from n/a through <= 3.1.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 · high confidenceA CSRF vulnerability in the WP-EasyArchives WordPress plugin (versions <= 3.1.2) allows attackers to craft malicious requests that result in Stored XSS. The lack of proper nonce validation on plugin actions enables attackers to trick authenticated administrators into executing unintended commands that inject persistent malicious scripts into the site.
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.
-
Locate WP-EasyArchives plugin filesNavigate to wp-content/plugins/ in your WordPress installation and check for a folder named 'wp-easyarchives' or similar variant. Alternatively, access Plugins > Installed Plugins in WordPress admin dashboard and search for WP-EasyArchives.Affected if The plugin folder exists in the plugins directory or the plugin appears in the WordPress admin plugin list.
-
Identify installed versionIf the plugin folder exists, open the main plugin PHP file (usually named wp-easyarchives.php or similar) and look for a version comment or header that states 'Version: x.x.x'. In WordPress admin, the plugin list displays version numbers next to each plugin.Affected if The displayed version number is 3.1.2 or lower.
-
Confirm plugin is activeIn WordPress admin dashboard, go to Plugins > Installed Plugins and verify whether WP-EasyArchives shows as 'Active' under the plugin status.Affected if The plugin is currently activated on the site.
-
Inspect admin action noncesExamine the main plugin PHP file for admin action handlers (like admin_post_, add_action calls with 'admin_init'). Check if nonce verification functions (wp_verify_nonce, check_admin_referer) are present before processing any $_POST or $_GET parameters that could modify data.Affected if No nonce verification is found before processing user-supplied input in admin action handlers, indicating the CSRF vulnerability is present.
If WP-EasyArchives version 3.1.2 or lower is installed and active, the environment is vulnerable to this CSRF-to-Stored XSS flaw.
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 dataUpdate WP-EasyArchives to the latest version which implements proper CSRF token validation and output escaping. Until a patch is available, disable the plugin or implement additional web application firewall rules to block suspicious requests targeting the plugin's admin actions.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49345 — 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-49345 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