CVE-2025-58997
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 Frenify Mow mow allows Code Injection.This issue affects Mow: from n/a through <= 4.10.
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 Cross-Site Request Forgery (CSRF) vulnerability in Frenify Mow mow (versions through 4.10) allows attackers to inject malicious code through forged requests. The high CVSS score (9.6) reflects the severe impact of successful code injection combined with the low complexity of CSRF attacks, which require tricking authenticated administrators into executing malicious requests.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
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 Mow theme is installedIn WordPress admin, go to Appearance > Themes to confirm the Frenify Mow theme is active or installed.Affected if The Mow theme is present in the WordPress installation.
-
Identify the installed Mow theme versionAccess the theme's style.css file via FTP or file manager (typically in wp-content/themes/mow/), or check the theme version displayed in the WordPress admin theme list.Affected if The version is 4.10 or lower.
-
Inspect admin action handlers for CSRF protectionReview the theme's PHP files (especially in admin/ or includes/ folders) for sensitive admin actions like settings updates, plugin activations, or file uploads. Search for functions handling form submissions and check if they validate nonces using wp_verify_nonce or check_admin_referer.Affected if Admin action functions are found without nonce verification.
-
Check AJAX endpoints for CSRF protectionIf the theme uses AJAX (look for wp_ajax_ hooks in PHP files), examine whether these endpoints verify nonces before processing requests.Affected if AJAX handlers process requests without verifying nonce tokens.
You are affected if the Frenify Mow theme version 4.10 or lower is installed and admin actions lack proper CSRF token validation.
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 dataApply available vendor patches for Frenify Mow mow immediately; if no patch exists, implement CSRF tokens and anti-CSRF measures on all state-changing operations, and consider disabling the product until a fix is released.
- 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-58997 — 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-58997 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