CVE-2025-28992
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 Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in snstheme SNS Anton snsanton allows PHP Local File Inclusion.This issue affects SNS Anton: from n/a through <= 4.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 confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the snstheme component of SNS Anton. The vulnerability allows attackers to include arbitrary local files via improper input validation in include/require statements, potentially exposing sensitive system files, configuration data, or source code.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/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 SNS Anton installation and versionLocate the main application directory and check for version information in files like version.php, composer.json, or a config file. Common paths include /var/www/html/ or the web root. Search for files containing 'SNS Anton' or 'anton' as the application name.Affected if The installed version of SNS Anton is unpatched and falls within the vulnerable range (check vendor for specific version boundaries).
-
Locate the snstheme componentSearch the SNS Anton installation for a directory or file named 'snstheme', 'theme', or similar. This component typically handles theming/layout functionality in PHP applications.Affected if The snstheme component is present in the installation and handles file inclusion logic.
-
Find vulnerable include/require statementsExamine PHP files in the snstheme component for include(), require(), include_once(), or require_once() statements that use variables or user input without sanitization. Look for patterns like 'include($theme)' or 'require($_GET["file"])' in the codebase.Affected if The snstheme component contains include/require statements that accept unsanitized input, allowing path traversal (e.g., ../../etc/passwd).
-
Verify parameter accessibilityDetermine if the vulnerable parameter (the variable used in include/require) can be controlled via HTTP request parameters, headers, or cookies. Test by attempting to pass a path like '../' or a known file path in the suspected parameter.Affected if The file inclusion parameter is directly accessible via HTTP (GET/POST) and accepts path traversal sequences without filtering.
You are affected if SNS Anton with the snstheme component is installed, the version is unpatched, and the vulnerable file inclusion parameter is accessible and accepts unsanitized path input.
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 patched version of SNS Anton (if available), or implement strict input validation with whitelist-based file inclusion logic to prevent path traversal and unauthorized file access.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-28992 — 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-28992 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