CVE-2025-24677
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 · uneditedImproper Control of Generation of Code ('Code Injection') vulnerability in wpspin Post/Page Copying Tool postpage-import-export-with-custom-fields-taxonomies allows Remote Code Inclusion.This issue affects Post/Page Copying Tool: from n/a through <= 2.0.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 · high confidenceA code injection vulnerability in the wpspin Post/Page Copying Tool plugin (postpage-import-export-with-custom-fields-taxonomies) versions through 2.0.3 allows remote code inclusion, enabling attackers to inject and execute malicious code on the affected WordPress site.
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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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.
-
Identify if the wpspin Post/Page Copying Tool plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins, or inspect the wp-content/plugins directory for folders named 'postpage-import-export-with-custom-fields-taxonomies' or containing 'wpspin'Affected if The plugin appears in the list of installed plugins or its directory exists in wp-content/plugins/
-
Check the installed plugin versionIn WordPress Plugins page, click on the plugin to view its details, or open the main plugin PHP file and look for the version header comment (e.g., 'Version: x.x.x')Affected if The displayed version is 2.0.3 or any earlier version (versions through 2.0.3 are affected)
-
Verify the plugin is activeIn WordPress admin > Plugins, confirm the plugin status shows 'Active' rather than 'Inactive' or 'Must-Use'Affected if The plugin is currently activated on the WordPress site
-
Check if the plugin import functionality is accessibleLook for the plugin menu item in the WordPress admin sidebar (often labeled Post/Page Copying Tool, Import, or similar) and confirm it is accessible to any user role with appropriate permissionsAffected if The import/Post copying tool feature is exposed and accessible on the site frontend or backend
-
Inspect for unexpected files or code injectionsReview wp-content/plugins/postpage-import-export-with-custom-fields-taxonomies/ for unknown .php files, or check recent modifications to plugin files via file system timestamps or version controlAffected if Suspicious files exist in the plugin directory or plugin files have been recently modified outside of legitimate updates
You are affected if the wpspin Post/Page Copying Tool plugin (postpage-import-export-with-custom-fields-taxonomies) is installed, active, and running version 2.0.3 or lower.
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 dataImmediately update the plugin to the latest version if a patch is available, or remove/uninstall the plugin if no update exists. Conduct a security audit to confirm no compromise has occurred.
- Consultation3.0 h
- Implementation3.0 h
- Testing2.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 $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24677 — 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-24677 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