CVE-2025-49353
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 Marcin Kijak Noindex by Path noindex-by-path allows Stored XSS.This issue affects Noindex by Path: from n/a through <= 1.0.
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 Noindex by Path WordPress plugin allows unauthenticated attackers to trick authenticated administrators into submitting malicious requests that inject stored XSS payloads into plugin settings, which then execute in the browsers of users viewing 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.
-
Verify Noindex by Path plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Noindex by Path' in the listAffected if The plugin appears in the installed plugins list, regardless of active or inactive status
-
Check installed plugin versionClick on the plugin name in the plugins list to view details, or check the plugin header in /wp-content/plugins/noindex-by-path/ directory via file manager or FTPAffected if The version shown is lower than the latest patched version released by the plugin developer
-
Examine plugin settings for suspicious contentNavigate to Settings > Noindex by Path (or the plugin's configuration page) and inspect all input fields, path entries, and text areas for unexpected JavaScript tags, event handlers, or encoded payloadsAffected if Any settings contain script tags, javascript: URIs, onload/onerror attributes, or other XSS payloads that were not intentionally added by an administrator
-
Check browser console for XSS warnings on plugin settings pageLoad the plugin settings page in a browser and open the developer console (F12), then look for any DOM-based XSS warnings or errorsAffected if Console displays XSS-related security warnings when viewing the settings page
-
Review .htaccess or robots.txt for unexpected noindex rulesCheck the site root .htaccess file and robots.txt for any noindex rules that were not intentionally configured by an administratorAffected if These files contain noindex directives for paths that were not deliberately added by the site owner
A user is affected if the Noindex by Path plugin is installed and either runs a version prior to the patched release, or if the plugin settings already contain injected XSS payloads from a CSRF attack.
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 to a patched version of Noindex by Path when released; meanwhile, implement anti-CSRF nonce validation on all form submissions and validate HTTP referer headers to prevent forged requests.
- 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-49353 — 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-49353 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