Estatik Mortgage CalculatorWordPress extension · Estatik
CVE-2023-28490
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 · uneditedUnauth. Reflected Cross-Site Scripting (XSS) vulnerability in Estatik Estatik Mortgage Calculator plugin <= 2.0.7 versions.
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 confidenceUnauthenticated reflected Cross-Site Scripting (XSS) vulnerability in the Estatik Mortgage Calculator WordPress plugin versions 2.0.7 and below. The vulnerability allows attackers to inject malicious scripts through unsanitized user inputs that are reflected back in the application's response without proper output encoding.
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
Estatik Mortgage CalculatorWordPress extension
<= 2.0.7CVSS 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.1/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.
-
Check installed plugin versionNavigate to WordPress Admin > Plugins > Installed Plugins > Locate 'Estatik Mortgage Calculator' and view the version number displayed under the plugin nameAffected if The version displayed is 2.0.7 or any version lower than 2.0.7
-
Verify plugin is activeIn the same plugins list, confirm the Estatik Mortgage Calculator plugin shows as 'Active'Affected if The plugin is active and the version is 2.0.7 or below
-
Identify vulnerable input parameterLocate the mortgage calculator form on the website frontend (typically on property listing pages). Inspect the HTML form elements to identify user-supplied parameters such as loan_amount, interest_rate, property_price, or similar fields used in the calculationAffected if The calculator form contains input fields that accept user-supplied values without visible server-side validation
-
Test for reflected output without encodingSubmit a test value containing a simple HTML tag (e.g., <img src=x onerror=alert(1)> ) in one of the calculator input fields and submit the form. Then examine the page response in the browser developer tools or view source to see if the raw HTML tag appears unencoded in the outputAffected if The submitted test value is reflected back in the page response as raw HTML/JavaScript without being entity-encoded (e.g., appears as <img rather than <img)
If the plugin version is 2.0.7 or below, the plugin is active, and user-supplied input is reflected in the response without proper HTML encoding, the environment is affected by this CVE.
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 dataUpdate the Estatik Mortgage Calculator plugin to the latest version if available, or implement proper input validation and output encoding for all user-supplied parameters to prevent script injection.
Fix this in Estatik Mortgage Calculator
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28490 — 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-2023-28490 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