CVE-2025-28897
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 Steveorevo Domain Theme domain-theme allows Stored XSS.This issue affects Domain Theme: from n/a through <= 1.3.
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 confidenceA CSRF vulnerability in the Steveorevo Domain Theme (versions 1.3 and below) allows attackers to trick authenticated administrators into submitting malicious requests that store XSS payloads in the database, which then execute when visitors view 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.
-
Identify Steveorevo Domain Theme installationCheck the theme directory (wp-content/themes/steveorevo-domain or similar) for theme files. Look for style.css with Theme Name: Steveorevo Domain Theme in the header comment.Affected if The theme directory exists and contains the Steveorevo Domain Theme files.
-
Determine installed theme versionOpen the theme's style.css file and locate the 'Version:' field in the theme header comment. Compare this version number to 1.3.Affected if The installed version is 1.3 or lower (e.g., 1.3, 1.2, 1.1, 1.0).
-
Locate admin forms that store data to databaseInspect theme template files (especially those in admin, includes, or template directories) for PHP code that handles form submissions and saves data to the WordPress database using functions like update_option, wp_insert_post, or custom table inserts.Affected if Theme contains PHP files with form handlers that accept user input and store it in the database without a separate admin page load.
-
Verify presence of anti-CSRF tokens in formsSearch the theme's PHP files for form submissions and check if they implement WordPress nonces (wp_nonce_field, wp_verify_nonce) or equivalent CSRF tokens. Look for nonce verification in form handling code.Affected if Forms that store data to the database lack nonce verification or use nonce verification inconsistently.
-
Check input sanitization on stored dataReview form handling code for sanitization functions (sanitize_text_field, esc_attr, sanitize_html_class, etc.) applied to user input before database storage.Affected if User-supplied data from forms is stored in the database without sanitization functions or with insufficient sanitization.
-
Inspect output encoding for stored dataExamine template files that display stored data (theme options, custom fields, widget content) for output encoding functions (esc_html, esc_attr, wp_kses_post) when rendering the stored values.Affected if Stored data is echoed to pages without proper output encoding, allowing stored XSS to execute.
If the installed version is 1.3 or below AND the theme contains admin-accessible forms that store data without CSRF tokens or proper sanitization/encoding, the environment is affected by this CVE.
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 dataAdd anti-CSRF tokens to all forms and state-changing operations in the theme, and implement proper input sanitization and output encoding for all user-supplied data before storage and display.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-28897 — 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-28897 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