dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-58980

MEDIUM · 5.3 CVSS v3.1 Published 2025-09-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Missing Authorization vulnerability in recorp Export WP Page to Static HTML/CSS export-wp-page-to-static-html allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Export WP Page to Static HTML/CSS: from n/a through <= 4.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 confidence

Missing authorization vulnerability in the Export WP Page to Static HTML/CSS WordPress plugin (versions <= 4.1.0) allows users to access export functionality that should be restricted by access control lists, potentially enabling unauthorized export of site content.

MitigationUpdate the plugin to the latest version as soon as a patch is released. Until then, disable the plugin if not actively needed, and restrict plugin access to administrator accounts only.

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify the plugin is installed
    Check for the presence of the 'export-wp-page-to-static-html-css' directory in /wp-content/plugins/ on the WordPress server, or list installed plugins via wp-cli: wp plugin list --status=active --format=csv
    Affected if The plugin directory exists in /wp-content/plugins/ or appears in the active plugin list
  2. Check the installed version
    Read the main plugin file (e.g., export-wp-page-to-static-html-css.php) and look for the 'Version:' header in the plugin comment block, or run: wp plugin list --search='export-wp-page-to-static-html-css' --format=json
    Affected if The reported version number is 4.1.0 or lower (e.g., 4.1.0, 4.0.9, 3.x.x)
  3. Confirm export functionality is accessible
    Attempt to access the plugin export URL endpoint (typically /wp-admin/admin-ajax.php?action=epwsthh_export or check the plugin source for registered AJAX actions) while logged in as a low-privilege user (e.g., editor, author, or subscriber), or inspect the plugin code for missing capability checks before export logic
    Affected if A non-administrator user can successfully trigger the export function or the plugin code lacks 'manage_options' or equivalent capability checks before executing export operations

If the plugin is installed at version 4.1.0 or below AND non-admin users can access or trigger the export functionality, the environment is affected by this authorization bypass.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to the latest version as soon as a patch is released. Until then, disable the plugin if not actively needed, and restrict plugin access to administrator accounts only.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-58980 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-58980 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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