CVE-2025-12461
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 · uneditedThis vulnerability allows an attacker to access parts of the application that are not protected by any type of access control. The attacker could access this path ‘…/epsilonnet/License/About.aspx’ and obtain information on both the licence and the configuration of the product by knowing which modules are installed.
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 confidenceThis is a broken access control vulnerability in an ASP.NET web application where the path '../epsilonnet/License/About.aspx' is accessible without authentication or authorization. An unauthenticated attacker can access this endpoint to retrieve sensitive information including license details, system configuration, and a list of installed modules.
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
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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.
-
Locate the epsilonnet application in your web rootSearch your web server document root directories for an 'epsilonnet' folder, or check your IIS/Apache/Nginx configuration for any application mapped to a path containing 'epsilonnet'.Affected if The epsilonnet folder or application virtual path exists on the server.
-
Verify the License/About.aspx file existsCheck if the file 'About.aspx' exists under the path 'epsilonnet/License/' in your web root, or attempt to access the URL 'https://yourdomain/epsilonnet/License/About.aspx' from an unauthenticated browser session.Affected if The file exists and the URL is reachable.
-
Test unauthenticated access to the endpointFrom a browser or curl command without providing any authentication cookies or credentials, attempt to access 'http[s]://[your-server]/epsilonnet/License/About.aspx'. Observe whether the page loads and displays license or configuration information.Affected if The page loads and exposes license details, system configuration, or module lists without requiring login.
-
Review web.config authorization settingsIf a web.config file exists in the epsilonnet directory, open it and inspect the <authorization> and <location> sections for the '/epsilonnet/License/About.aspx' path. Check if any allow/deny rules are defined.Affected if No authorization rules are defined, or the rules explicitly allow unauthenticated users (allow users='*' or allow users='?').
Your environment is affected if the epsilonnet application is installed with the License/About.aspx endpoint accessible without any authentication credentials.
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 dataImplement proper authentication and authorization controls on the '/epsilonnet/License/About.aspx' endpoint to ensure only authorized users can access license and configuration information.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12461 — 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-12461 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