The CBC IV attack does more than that.
If I guess the plaintext corresponding to any ciphertext block I've seen before, and can predict a future IV, I can verify my guess by submitting a suitable message to be encrypted with that IV. Obviously, that could be bad if, say, I knew the plaintext to be either "yes" or "no", and only needed to find out which one it is.
More concretely, the BEAST attack for example allows the recovery of cookies sent by a web browser over HTTPS. The way it works is (more or less) that you first convince the browser to send an HTTPS request where a block boundary falls just after the first unknown byte in the cookie (e.g. by adjusting the length of the requested URL) and intercept the ciphertext.
So now you have a ciphertext block that you know corresponds to, say, the string
Cookie: secret=X, where
X is an unknown byte. Now you use the CBC IV attack to test all possible values of
X and find the right one. Then you repeat the process with a URL that's one byte shorter, so that you get a ciphertext block corresponding to
ookie: secret=XY, where you now know
X but don't yet know
Y. Then just keep repeating the process until you've recovered the entire cookie, byte by byte.
See this answer to a related question for more details.