CVE-2025-30975
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 SaifuMak Add Custom Codes add-custom-codes allows Code Injection.This issue affects Add Custom Codes: from n/a through <= 4.80.
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 code injection vulnerability exists in the SaifuMak Add Custom Codes plugin (versions <= 4.80) where improper control of code generation allows attackers to inject malicious code through the add-custom-codes functionality. The vulnerability stems from insufficient input validation on user-supplied data that gets dynamically executed.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/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 SaifuMak Add Custom Codes plugin is installedReview your site's plugin directory or CMS plugin list to confirm the presence of the SaifuMak Add Custom Codes pluginAffected if The plugin appears in the list of installed plugins
-
Check the installed plugin versionView the plugin details in your CMS plugin management interface or inspect the plugin's main file header for the version numberAffected if The reported version is 4.80 or lower
-
Verify if the add-custom-codes functionality is enabledAccess the plugin settings panel and locate the add-custom-codes feature configuration; check whether it is activated or set to activeAffected if The add-custom-codes feature is enabled or active in the plugin settings
-
Confirm the code generation endpoint is accessibleTest access to the plugin's code injection endpoint (commonly found at /wp-admin/admin-ajax.php?action=add-custom-code or similar URL patterns used by the plugin)Affected if The endpoint returns a valid response indicating it is publicly or non-admin accessible
-
Inspect plugin configuration for dynamic code execution settingsReview the plugin's configuration files or settings panel for any options that allow dynamic code generation or execution of user-supplied inputAffected if Dynamic code execution options are present and not explicitly disabled
You are affected if the SaifuMak Add Custom Codes plugin is installed with version 4.80 or lower AND the add-custom-codes functionality is enabled and accessible.
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 dataUpgrade to a version beyond 4.80 if available; otherwise, disable the add-custom-codes functionality and implement strict input validation/sanitization on all code generation endpoints.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30975 — 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-30975 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