CVE-2025-12140
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 · uneditedThe application contains an insecure 'redirectToUrl' mechanism that incorrectly processes the value of the 'redirectUrlParameter' parameter. The application interprets the entered string of characters as a Java expression, allowing an unauthenticated attacer to perform arbitrary code execution. This issue was fixed in version wu#2016.1.5513#0#20251014_113353
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 confidenceThe application has an insecure 'redirectToUrl' mechanism that evaluates the 'redirectUrlParameter' parameter as a Java expression (similar to an eval() vulnerability). An unauthenticated attacker can send a crafted string that gets interpreted as Java code, enabling arbitrary 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
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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.
-
Identify the application and versionReview your application deployment artifacts (WAR file manifest, JAR metadata, or service banner) to determine the product name and installed version. Compare against the fixed version wu#2016.1.5513#0#20251014_113353Affected if The installed version is unknown, unconfirmed, or earlier than the fixed release
-
Locate the redirectToUrl mechanismSearch application source code or decompiled classes for methods named 'redirectToUrl' that process the 'redirectUrlParameter' parameter. Inspect the method implementation to see if it evaluates the parameter as a Java expressionAffected if The redirectToUrl method exists and directly evaluates redirectUrlParameter without safelisting or input validation
-
Confirm parameter accessibilityReview your web application's exposed endpoints, servlets, or controllers to verify the redirectUrlParameter is reachable via HTTP request without authenticationAffected if The redirectUrlParameter can be passed in an HTTP GET or POST request to an unauthenticated endpoint
-
Test for expression evaluationSend a test request with redirectUrlParameter containing a benign expression such as ${7*7} or ${T(java.lang.System).exit(0)} (in a non-production test environment only) and observe if the expression is evaluated rather than treated as a literal stringAffected if The application returns the evaluated result (49) or executes the expression instead of redirecting to the literal string
If the redirectToUrl mechanism evaluates the redirectUrlParameter as a Java expression (confirmed via test payload), the environment is affected by CVE-2025-12140
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 dataImmediately upgrade to version wu#2016.1.5513#0#20251014_113353 or later. Until patching is possible, network-level restrictions on the affected endpoint should be implemented.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12140 — 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-12140 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