hardmulti selectObjective-mapped

During testing of a shopping portal, a POST request to /api/address/update succeeds even when the anti-CSRF token is removed. In a separate test, changing customerId=1842 to customerId=1843 in a GET request returns another user's invoice data. Which two vulnerabilities are present? Select two.

Question 1hardmulti select
Full question →

During testing of a shopping portal, a POST request to /api/address/update succeeds even when the anti-CSRF token is removed. In a separate test, changing customerId=1842 to customerId=1843 in a GET request returns another user's invoice data. Which two vulnerabilities are present? Select two.

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Best answer

Cross-site request forgery is present because the state-changing request works without a valid anti-CSRF token.

If a state-changing request succeeds without a valid anti-CSRF token, the application is not reliably verifying that the request originated from the intended user session. That makes the action vulnerable to cross-site request forgery, where a malicious site can induce a logged-in user to submit an unauthorized request.

B

Best answer

Broken access control or IDOR is present because changing customerId reveals another user's invoice.

Changing an object identifier and gaining access to another user's data is a textbook broken access control issue, often described as IDOR. The server is trusting the client-supplied identifier without enforcing ownership or authorization checks. That means a user can reach records they should not be able to view.

C

Distractor review

SQL injection is present because the customerId value changes in the URL.

A parameter changing from one integer to another does not by itself indicate SQL injection. SQL injection would require evidence that the application is interpreting malicious SQL syntax, such as quotes, comments, or database error behavior. Here, the clue is unauthorized object access, not database query manipulation.

D

Distractor review

Cross-site scripting is present because the invoice data is returned in the browser.

Receiving another user's invoice in the browser is not evidence of script injection. Cross-site scripting requires malicious script execution in a victim's browser context. The scenario describes unauthorized data disclosure through an identifier change, which is an access-control problem rather than a content-injection issue.

E

Distractor review

Insecure deserialization is present because the request uses JSON-like parameters.

The presence of request parameters or JSON formatting does not imply insecure deserialization. That weakness involves tampering with serialized objects or object state during parsing. The scenario provides no evidence of object deserialization, integrity bypass, or gadget-chain exploitation.

Common exam trap

Common exam trap: authentication is not authorization

Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.

Technical deep dive

How to think about this question

This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.

KKey Concepts to Remember

  • Authentication checks who the user is.
  • Authorization controls what the user is allowed to do after login.
  • Privilege levels affect access to EXEC and configuration commands.
  • AAA, TACACS+ and RADIUS can separate login success from command access.

TExam Day Tips

  • Do not assume successful login means full administrative access.
  • Look for words such as cannot enter configuration mode, privilege level, authorization or command access.
  • Separate login problems from permission problems before choosing the answer.

Related practice questions

Related SY0-701 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this SY0-701 question test?

Authentication checks who the user is.

What is the correct answer to this question?

The correct answer is: Cross-site request forgery is present because the state-changing request works without a valid anti-CSRF token. — Two separate flaws are shown. The first is CSRF because the server accepts a state-changing request after the anti-CSRF token is removed. The second is broken access control, specifically an IDOR-style issue, because changing the customer identifier exposes another user's invoice. Together, these behaviors show that the application does not properly verify request origin or user authorization. Why others are wrong: The scenario does not show SQL injection, XSS, or insecure deserialization. There are no malicious SQL characters, no script execution, and no serialized-object tampering. The key signals are the missing CSRF protection on a state change and the ability to access another user's object by editing an identifier, which are access-control weaknesses rather than injection flaws.

What should I do if I get this SY0-701 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.