CVE-2025-66533
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 StellarWP GiveWP give allows Code Injection.This issue affects GiveWP: from n/a through <= 4.13.1.
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 confidenceCode injection vulnerability in GiveWP plugin allows attackers to inject and execute malicious code through improper handling of user input. This type of vulnerability typically occurs when application includes untrusted data in a way that alters program execution, potentially enabling arbitrary PHP code execution on the server.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed GiveWP versionIn WordPress admin, go to Plugins > GiveWP and view the version number displayed, or check the version in the plugin's main PHP file header (givewp.php)Affected if The installed version is lower than 4.13.1 (the fixed version)
-
Verify GiveWP plugin is activeCheck the WordPress plugins page to confirm GiveWP is activated on the siteAffected if GiveWP is active and the version is vulnerable
-
Confirm donation/form features are in useCheck if any GiveWP donation forms or campaigns are published on the site by viewing active forms in GiveWP > DonationsAffected if Donation forms accepting user input are published and accessible to unauthenticated users
-
Check for suspicious admin activityReview WordPress admin user accounts for unexpected additions or modifications, and check server access logs for unusual POST requests to /?give-api= endpointsAffected if Unexpected admin users exist or unusual GiveWP API requests are logged
-
Inspect uploaded files directoryExamine the wp-content/uploads/give/ directory for unexpected PHP files or scripts that may have been injectedAffected if Unexpected PHP files or scripts are found in the uploads directory
A site is affected if GiveWP plugin version is below 4.13.1, the plugin is active, and donation forms accepting user input are accessible, allowing potential code injection via improper input handling.
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 dataUpdate GiveWP to the latest version beyond 4.13.1 that contains the security patch. Additionally, review and restrict file upload capabilities and implement proper input validation as a defense-in-depth measure.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66533 — 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-66533 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