CVE-2025-53274
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 Hossin Asaadi WP Permalink Translator wp-permalink-translator allows Stored XSS.This issue affects WP Permalink Translator: from n/a through <= 1.7.6.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the WP Permalink Translator WordPress plugin allows attackers to trick authenticated administrators into performing unintended actions that result in Stored XSS. The plugin lacks proper anti-CSRF tokens on forms and does not sufficiently sanitize/escape user input, enabling malicious scripts to be stored and executed when other users access affected pages.
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.
-
Confirm plugin installationCheck for the WP Permalink Translator plugin in your WordPress installation at wp-content/plugins/ or via the WordPress admin dashboard under PluginsAffected if The plugin is installed and active in WordPress
-
Identify the installed versionOpen the main plugin file (usually permalink-translator.php or similar) and locate the version defined in the plugin header comment; compare this version to the latest version available in the WordPress plugin repositoryAffected if The installed version is older than the patched version released to address CVE-2025-53274
-
Verify CSRF protection on plugin formsInspect the plugin PHP files for form submissions (particularly in admin settings pages) and check if WordPress nonces are being verified using functions like wp_verify_nonce(), check_admin_referer(), or wp_nonce_field()Affected if Forms in the plugin do not implement nonce verification (anti-CSRF tokens)
-
Check input sanitization in plugin codeReview the plugin PHP files that handle user input (especially settings pages and any input that gets stored) for use of sanitization functions like sanitize_text_field(), esc_attr(), esc_html(), or prepared database queriesAffected if User input is not properly sanitized before storage or output, allowing unsanitized data to be saved to the database
A user is affected if the WP Permalink Translator plugin is installed, the version lacks the CVE-2025-53274 fix, and the plugin's forms lack CSRF nonce verification combined with inadequate input sanitization enabling Stored XSS.
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 anti-CSRF tokens (nonces) on all form submissions and AJAX requests within the plugin, combined with proper output escaping/sanitization of all user inputs to prevent XSS. Users should update to the latest plugin version when available.
- 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-53274 — 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-53274 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