CVE-2025-13134
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 · uneditedThe AuthorSure plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.3. This is due to missing or incorrect nonce validation on the 'authorsure' page. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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 confidenceThe AuthorSure WordPress plugin versions up to 2.3 lacks proper nonce validation on the 'authorsure' admin page, allowing unauthenticated attackers to forge requests that can modify plugin settings and inject malicious web scripts. The attack requires social engineering to trick an administrator into clicking a malicious link, leveraging the trusted context of an authenticated admin session.
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
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Locate the AuthorSure plugin installationIn WordPress, check /wp-content/plugins/authorsure/ directory, or view the installed plugins list in the WordPress admin dashboard under Plugins > Installed PluginsAffected if The AuthorSure plugin is present in the WordPress installation
-
Determine the installed version of AuthorSureCheck the plugin header comment in the main plugin file (usually authorsure.php) for the 'Version' field, or view the version in the WordPress plugins admin listAffected if The version number is 2.3 or lower (e.g., 2.3, 2.2, 2.1, etc.)
-
Verify the plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and confirm the AuthorSure plugin is activatedAffected if The plugin is active and the version is 2.3 or lower - the CSRF vulnerability is present in active installations
-
Confirm the vulnerability conditionThe vulnerability exists regardless of configuration because it stems from missing nonce validation on the 'authorsure' admin page. Any WordPress site running AuthorSure version 2.3 or below with an authenticated administrator session is susceptible to CSRF attacks via social engineeringAffected if The site runs AuthorSure version 2.3 or below and has an authenticated administrator session that could be exploited
A WordPress site is affected if the AuthorSure plugin is installed and active at version 2.3 or lower, as this version lacks proper nonce validation on the authorsure admin page, allowing CSRF-based setting modifications.
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 AuthorSure to version 2.4 or later which implements proper nonce validation. Until patched, administrators should avoid clicking untrusted links and consider implementing additional CSRF protections at the server level.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13134 — 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-13134 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