Web App & API Testing

Four High-severity flaws found and fixed before a finance portal launched

Client
Financial services company
Service
Web application penetration testing
Focus
Card data and business logic
Verified
Critical and High fixed; retested by ioSENTRIX
The challenge

What did the client need?

A financial services company built a multi-user web portal for its corporate customers to manage their finances. Because the team had built it in-house, it wanted an outside view before launch.

Engagement details

Client
Financial services company
Product
Multi-user web portal where corporate customers manage their finances
Scope
The web application and the servers that handle and store customer data
Driver
An outside view of an application built in-house
Verified
Critical and High fixed; retested by ioSENTRIX
Tested by
ioSENTRIX application security testers
Our approach

How did ioSENTRIX approach it?

Our testers mapped every page and parameter, then used each feature the way both a customer and an attacker would, including the referral flow built to bring in new customers.

Also High: cross-site request forgery and a business-logic flaw in the portal’s workflows. The rest were Medium, Low and informational findings across the application and its servers.

What we found

What did ioSENTRIX find?

Card data in responses and phishing through the portal itself, both fixed before launch.

HighFinding 1

Card numbers came back in HTTP responses

Credit card numbers were included in the portal’s HTTP responses, where anyone with access to the browser or the traffic could read them, whatever the page itself displayed.

Business impact. Payment card data that should never leave the server in readable form was exposed.

HighFinding 2

The referral feature could carry an attacker’s phishing

Users could change the referral message without restriction. A message sent through the portal’s own referral feature could carry an attacker’s text and links.

Business impact. Phishing would arrive from a trusted, legitimate sender, the portal itself, aimed at the company’s own prospects.

Two High-severity paths found before launch
Path 1 · card data · High
  1. 1Portal usednormal requests
  2. 2Response sentwith card numbers
  3. 3Data readablein browser or traffic
Path 2 · referral phishing · High
  1. 1Message editedno restriction
  2. 2Portal sends ittrusted sender
  3. 3Prospect clicksattacker’s link
Outcome: Exposure (card data and customer trust)
The impact

What changed as a result?

Our testers found more than 25 issues, four of them High. Credit card numbers were exposed in HTTP responses, and the portal’s referral feature could be turned into a phishing tool. The in-house team fixed every High finding before launch, and ioSENTRIX retested the fixes.

25+
findings across the portal and its servers
4
High-severity findings, all fixed before launch
1
referral feature that could send phishing from a trusted sender

How many findings, and how severe?

25+ findings in total, including 4 High.

  • High 4
  • Medium
  • Low
  • Info

What changed after the test?

What changed before launch
AreaBefore the testAfter remediation
Card dataCredit card numbers exposed in HTTP responsesExposure removed; fix retested by ioSENTRIX
Referral messagesMessage text could be changed without restrictionFixed by the in-house team; retested by ioSENTRIX
Requests and workflowsCross-site request forgery and a business-logic flawBoth fixed and retested before launch

✓ Verification: All High findings fixed before launch; retested by ioSENTRIX.

Key insight

The most dangerous feature was the one built to bring in new customers.

Lessons

Lessons for financial services teams

01

Never send what the page should not show

Card numbers in a response are exposed even if the screen hides them. Mask or drop sensitive data on the server.

Finding 1
02

Treat user-editable content as a channel

A referral message anyone can rewrite is a phishing tool with your name on it. Restrict what users can change.

Finding 2
03

Test features as an attacker would use them

The referral flow was built for growth. Testing it as an abuse path found the risk before customers did.

Approach · OWASP Web Security Testing Guide, 4.10 Business Logic
Next step

Launching a financial application? See a sample web application test report or book a strategy session before go-live.

Service
Web application and API penetration testing
Explore the service

Details in this case study are anonymised and generalised. Methods that could harm other products are withheld.

FAQ

Frequently asked questions

What did ioSENTRIX test in this case study?

A financial services company built a multi-user web portal for its corporate customers to manage their finances. Because the team had built it in-house, it wanted an outside view before launch.

What was the most serious issue?

Card numbers came back in HTTP responses. Payment card data that should never leave the server in readable form was exposed.

How many findings were there, and how severe?

25+ findings in total, including 4 High.

Were the fixes verified?

All High findings fixed before launch; retested by ioSENTRIX.

Which ioSENTRIX service does this case study cover?

Web application and API penetration testing, delivered by the ioSENTRIX application security testers.

Which standards does this align with?

OWASP Web Security Testing Guide, 4.10 Business Logic. These are cited as alignment guidance, not a compliance claim.

How to get started

Ready to strengthen your security? Fill out our quick form, and a cybersecurity expert will reach out to discuss your needs and next steps.
DecorativeDecorative