CVE-2025-26577
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 daxiawp DX-auto-publish dx-auto-publish allows Stored XSS.This issue affects DX-auto-publish: from n/a through <= 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 · low confidenceCSRF vulnerability in the DX-auto-publish WordPress plugin allows authenticated or unauthenticated attackers to trick administrators into submitting malicious requests that result in stored XSS, persisting malicious scripts in the plugin's data that execute when other users view the affected content.
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 DX-auto-publish plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'DX-auto-publish' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'dx-auto-publish' or similar.Affected if The plugin is installed and active on the WordPress site
-
Identify the installed versionIn WordPress adminPlugins list, locate the DX-auto-publish entry and read the version number displayed beneath the plugin name. Alternatively, check the main plugin file header in /wp-content/plugins/[plugin-folder]/dx-auto-publish.php for the 'Version' tag.Affected if The version is unknown, unpatched, or within any vulnerable range (compare against official CVE references)
-
Inspect plugin-stored data for suspicious scriptsQuery the WordPress options table (wp_options) for any option_name containing 'dx_auto_publish' or the plugin's slug. Use SQL: SELECT * FROM wp_options WHERE option_name LIKE '%dx_auto_publish%'. Review the option_value for any encoded or raw JavaScript, iframe, or script tags.Affected if Any stored XSS payloads exist in the plugin's database options, indicating the vulnerability was exploited
-
Check admin menu for plugin functionalityIn WordPress admin, locate the DX-auto-publish menu item (typically under Posts, Settings, or a dedicated plugin menu). Access any admin pages the plugin provides to see if user-submitted content or settings are displayed without proper escaping.Affected if The plugin displays user-contributed content that may execute unescaped scripts when viewed by other users
If DX-auto-publish is installed and active, the site is potentially affected since the CSRF flaw allows any state-changing admin action to be forged, leading to stored XSS persistence in plugin data.
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) for all state-changing admin actions and apply proper input sanitization plus output escaping to prevent stored XSS.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26577 — 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-26577 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