CVE-2018-14924
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 · uneditedMatera Banco 1.0.0 is vulnerable to multiple stored XSS, as demonstrated by the sca/privilegio/consultarUsuario.jsf "Nome Completo" (aka user fullname) field.
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 confidenceMatera Banco 1.0.0 contains a stored cross-site scripting (XSS) vulnerability in the user management interface. The 'Nome Completo' (Full Name) field on the sca/privilegio/consultarUsuario.jsf page does not properly sanitize user input, allowing malicious scripts to be stored and executed when other users view the user profile.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0.0CVSS 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
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Confirm Matera Banco versionIdentify the installed version of Matera Banco in your environment by checking the application metadata, about page, or system information. This may be found in the application configuration files, deployment descriptors, or the application's footer/about section.Affected if The installed version is Matera Banco 1.0.0 specifically.
-
Verify user management interface accessibilityAttempt to access the path /sca/privilegio/consultarUsuario.jsf in your Matera Banco installation. This can be done via web browser or by checking if the endpoint responds to HTTP requests.Affected if The page is accessible and returns a valid HTTP response (not 404 or 403).
-
Confirm user profile modification privilegesCheck if the current user account has permission to access the user management interface and modify user profiles, specifically the 'Nome Completo' (Full Name) field. This typically requires administrative or user management roles.Affected if You have privileges to access the user management interface and modify user profile fields.
-
Test field for unsanitized input storageIf you have modification privileges, submit a benign test payload such as <script>alert('XSS')</script> or <img src=x onerror=alert(1)> in the 'Nome Completo' field and save the profile. Then view the profile again to observe if the payload renders as HTML/JavaScript instead of being encoded or stripped.Affected if The submitted script tags or event handlers execute as JavaScript when the profile is displayed, confirming the input is stored and rendered without proper sanitization.
You are affected if you are running Matera Banco version 1.0.0, have access to the user management interface, and can confirm that the 'Nome Completo' field does not sanitize or encode malicious script content.
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 input validation and output encoding for the 'Nome Completo' field. Use a whitelist approach for allowed characters and apply context-aware HTML encoding when displaying user-supplied data to prevent script execution.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-14924 — 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-2018-14924 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