dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2025-10247

MEDIUM · 6.3 CVSS v3.1 Published 2025-09-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A security vulnerability has been detected in JEPaaS 7.2.8. This vulnerability affects the function doFilterInternal of the component Filter Handler. Such manipulation leads to improper access controls. The attack can be executed remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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 confidence

JEPaaS 7.2.8 contains an improper access control vulnerability in the Filter Handler component's doFilterInternal function. This servlet filter implementation fails to properly enforce authentication or authorization checks, allowing remote attackers to bypass access controls. The vulnerability is exploitable remotely and public exploits are available.

MitigationImplement proper access control validation in the Filter Handler's doFilterInternal method to ensure all requests are authenticated and authorized before processing. This typically involves reviewing the filter chain configuration, adding appropriate role/permission checks, and ensuring the filter executes for all protected endpoints.

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
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm JEPaaS installation
    Look for JEPaaS directories (e.g., jepaas, JEPaaS) in common installation paths such as /opt, /var/www, or C:\Program Files. Check for running Java processes listening on web ports (typically 8080, 8443) that serve JEPaaS applications.
    Affected if JEPaaS software is found running in the environment
  2. Identify installed JEPaaS version
    Locate the version file or about page within the JEPaaS installation. Common paths include version.properties, about.jsp, or the administration panel. Compare the version number to the affected release (7.2.8).
    Affected if The installed version is 7.2.8 or falls within an unpatched 7.x release line
  3. Locate Filter Handler component
    Inspect the web application's web.xml deployment descriptor (typically in WEB-INF/web.xml) for a filter named 'Filter Handler' or similar. Also check for custom filter implementations in the application's classpath that handle the doFilterInternal method.
    Affected if The Filter Handler servlet filter is present and configured in the application
  4. Verify filter chain configuration
    Examine the filter mapping in web.xml to determine which URL patterns the Filter Handler intercepts. Check if the filter is mapped to cover all endpoints or if certain paths are explicitly excluded from authentication filtering.
    Affected if The filter is mapped but allows unauthenticated access to protected endpoints or has broad exclusions
  5. Test for authentication bypass
    Send HTTP requests to protected JEPaaS endpoints (such as /api/, /admin/, or authenticated workflows) without providing valid authentication credentials. Observe whether the request is processed or rejected.
    Affected if Requests to protected resources succeed without authentication credentials

If JEPaaS version 7.2.8 (or an unpatched 7.x version) is running with the Filter Handler component enabled and unauthenticated requests can access protected endpoints, the environment is affected by this CVE.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper access control validation in the Filter Handler's doFilterInternal method to ensure all requests are authenticated and authorized before processing. This typically involves reviewing the filter chain configuration, adding appropriate role/permission checks, and ensuring the filter executes for all protected endpoints.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10247 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-10247 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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